Dan,
Thanks for the info.
I believe that a large part of the problem was using the door and dwr knobs. Since I have taken them off the cabinets, the virtual memory doesn't seem to be a problem.
Thanks for the help.
John
I need help with a crashing file
Moderators: Jason Susnjara, Larry Epplin, Clint Buechlein, Scott G Vaal, Jason Susnjara, Larry Epplin, Clint Buechlein, Scott G Vaal
-
JohnLashuay
- Guru Member
- Posts: 645
- Joined: Mon, Nov 20 2006, 3:39PM
- Company Name: Rylex Custom Cabinetry-Close
- Country: UNITED STATES
- Location: Pine Island, New York
- Contact:
-
DanEpps
- Wizard Member
- Posts: 5852
- Joined: Thu, Jul 28 2005, 10:18AM
- Company Name: Dan Epps
- Country: UNITED STATES
- Location: Rocky Face GA
Good point Al! There certainly is a (very murky) point of diminishing return for virtual memory size.
Here is how Windows works in a nutshell: Every process gets 4GB of virtual address space allocated to it. Notice this is virtual address space, not virtual memory. To analogize, address space is like a new subdivision. All the lots have been given addresses regardless of whether a house has been built on them or not. Once a house is built on a lot, the \"virtual address\" becomes a real address for that house.
Not every Windows process uses all of the 4GB allocated to it. Those that do and still want more, die. That's it, 4GB is the maximum that can be allocated by the operating system.
The amount of physical memory (or RAM) on your computer, combined with the number of running processes, determines when virtual memory (paging or swap space) is allocated. Computers with lots of RAM and few running processes need little virtual memory. On the other hand, computers with less RAM or lots of running processes need larger virtual memory.
It is here that it starts to become complicated. RAM is always faster than virtual memory (disk), so having lots of RAM makes your system faster, right? To a point this is true. If you are running a server operating system and have, say 32GB of RAM, you don't need much virtual memory. The problem is that Windows XP can only address 3GB of RAM (4GB, but 1GB is reserved). Every process is given 4GB of address space, so what happens when the demands of all runing processes need more than 3GB of RAM? Virtual memory is used.
Since Windows XP can address only 3GB of RAM, that is the \"rule of thumb\" optimum amount of virtual memory. Making it a static size keeps Windows from having to expand virtual memory when more is needed. Expanding virtual memory causes running processes to be put to sleep for the duration of the expansion process.
This is fine except that Windows is not terribly good at estimating just how much to expand virtual memory. Expansion takes place one disk allocation unit (8MB) at a time. As soon as it is expanded, the operating system revives the sleeping processes, which then grab the newly expanded swap space. Now the system needs more and everything is put to sleep again while another 8MB is added to the virtual memory file. This goes on until no more virtual memory is needed. It can take quite a while if the amount needed is very large.
Back to your original question--when to say when. In my experimentation I have found 3GB (3072MB) to give about the best performance with eCabinets. Less requires Windows to expand virtual memory and more is not really being used.
I hope this helps without being too geeky
Here is how Windows works in a nutshell: Every process gets 4GB of virtual address space allocated to it. Notice this is virtual address space, not virtual memory. To analogize, address space is like a new subdivision. All the lots have been given addresses regardless of whether a house has been built on them or not. Once a house is built on a lot, the \"virtual address\" becomes a real address for that house.
Not every Windows process uses all of the 4GB allocated to it. Those that do and still want more, die. That's it, 4GB is the maximum that can be allocated by the operating system.
The amount of physical memory (or RAM) on your computer, combined with the number of running processes, determines when virtual memory (paging or swap space) is allocated. Computers with lots of RAM and few running processes need little virtual memory. On the other hand, computers with less RAM or lots of running processes need larger virtual memory.
It is here that it starts to become complicated. RAM is always faster than virtual memory (disk), so having lots of RAM makes your system faster, right? To a point this is true. If you are running a server operating system and have, say 32GB of RAM, you don't need much virtual memory. The problem is that Windows XP can only address 3GB of RAM (4GB, but 1GB is reserved). Every process is given 4GB of address space, so what happens when the demands of all runing processes need more than 3GB of RAM? Virtual memory is used.
Since Windows XP can address only 3GB of RAM, that is the \"rule of thumb\" optimum amount of virtual memory. Making it a static size keeps Windows from having to expand virtual memory when more is needed. Expanding virtual memory causes running processes to be put to sleep for the duration of the expansion process.
This is fine except that Windows is not terribly good at estimating just how much to expand virtual memory. Expansion takes place one disk allocation unit (8MB) at a time. As soon as it is expanded, the operating system revives the sleeping processes, which then grab the newly expanded swap space. Now the system needs more and everything is put to sleep again while another 8MB is added to the virtual memory file. This goes on until no more virtual memory is needed. It can take quite a while if the amount needed is very large.
Back to your original question--when to say when. In my experimentation I have found 3GB (3072MB) to give about the best performance with eCabinets. Less requires Windows to expand virtual memory and more is not really being used.
I hope this helps without being too geeky
! NOW I understand the virtual memory issue a whole lot better.