[…] because Windows will move pages from RAM to the pagefile only when necessary.
Sorry, that’s 100% pure bullshit. While this was true in the good old times (with NT4, for example), modern operating systems (and this includes XP) use precleaning. Precleaning is a strategy where the OS writes dirty pages to the pagefile even if there is plenty of free RAM. These pages are then kept in RAM and the pagefile simultaneously. If the application needs them, fine, they are still in RAM. If memory usage suddenly increases and the system needs virtual memory (like when a huge application gets started), the precleaned pages are already in the swapfile and the system doesn’t have to wait until they are swapped out. Looks like a win-win situation, right?
Actually, not quite. Since some pages get dirty all the time (for example, by an application which just displays the current time…), precleaning happens all the time as well. The disk with the pagefile is therefore accessed frequently. For a mobile computer (laptop or whatever runs on batteries), this means increased battery drain. For an office PC, this means increased an noise level because the disk never spins down, even when the machine is not in use.
Furthermore, you gain no performance improvement by turning off the pagefile.
Oops, bullshit again! Agreed, the additional I/O load which is caused by precleaning is quite low and usually doesn’t hamper the system performance very much (unless you consider battery power consumption as a part of system performance). However, real life seems not to agree with the bright and happy theory. File caching, for example, uses RAM and may use precleaned pages if they are available. Well, bad luck for any precleaned page which gets claimed for such a purpose but needs to be in memory just a few milliseconds later…and such things happen because the OS can not really guess where the user will click next, and which page will then be needed. Well-meant caching strategies can in these cases kill the system’s performance. With virtual memory disabled, caching will be decreased when free RAM decreases.
Now, what is better: less caching or more virtual memory? Your mileage may vary, but my experience (and that of quite a number of other people as well) shows that DISABLING vortual memory on boyes with 4GB is beneficial. Not only with XP. On a 4GB Server 2003 TS for example, the difference is dramatic: without VM, Eclipse works smootly, with VM, Eclipse often requires several seconds (!) to process a single mouse click!
Best regards, Klaus