up vote 6 down vote favorite
share [g+] share [fb]

I would have thought this was already asked but I can't seem to find it.

At what point do I no longer need virtual memory enabled? With 4GB of RAM I see that the computer rarely uses anywhere near all of it. At that point virtual memory isn't strictly necessary. Is there danger in turning it off? Are there features I'll lose if I do?

link|improve this question
70% accept rate
Attention: There is only a limited amount of memory given to drivers, called the non-paged and paged pool memory sections. A page file is necessary for when the paged section gets full, as a gamer I have seen a game complain about paged pool memory just because I had my page file disabled on a 8 GB system. Conclusion: Page files are necessary, they prevent paged pool depletion and actually do speed up your system. – Tom Wijsman Oct 24 '11 at 16:28
feedback

5 Answers

up vote 5 down vote accepted

Since memory is not exactly a sparse resource on desktop PCs / laptops anymore, I doubt that most programs can handle out-of-memory conditions gracefully and will crash instead.
So: Dangerous? Yes, if your 4GB are used up somehow and you have no pagefile, applications may start to crash.
And as shown in Zoran's example it may be hard to identify the problem later on.

The article, that Ram refers to, also states, that turning swapping off usually doesn't improve speed and may do the opposite instead:

So while there may be some workloads that perform better with no paging file, in general having one will mean more usable memory being available to the system

link|improve this answer
feedback
up vote 8 down vote

See Mark Russinovich's article on Virtual Memory. That should give you a good pointer about Virtual Memory

link|improve this answer
+1 for Mark Russinovich reference. Always a great read. – mrduclaw Dec 14 '09 at 19:49
feedback
up vote 2 down vote

This classic post on ServerFault has some good points. For only 4GB I'd leave the pagefile alone, and the space involved on the disk is minor in any case.

link|improve this answer
feedback
up vote 2 down vote

I'd recommend to leave the virtual memory settings to their default. I have 8GB of RAM and turned virtual memory off thinking I would gain in speed (because of no swapping), but it turns out that made my system less stable (and I did this on 2 machines, similar result). I was experiencing one BSOD per week approximately, on both machines. I started examining the minidumps produced and found out that all the BSODs were triggered by a call to a routine called KiPageFault. So I tried setting the virtual memory settings back to their defaults, and the regular BSODs disappeared.

Took me quite a while to correlate the 2, and I have no actual evidence that the fact that I turned off virtual memory caused the BSODs, but my machines were more stable after I turned it back on...

link|improve this answer
Thanks. It is good to hear real results and not just suppositions. – Steve Rowe Oct 15 '09 at 1:34
feedback
up vote 0 down vote

Depends what your workload is. I've set up a bunch of diskless frontends for a web application. They network booted and ran everything they needed within 8GB of ram.

I've also used windows (98 probably) with 32MB and no pagefile - of course you have to live in that memory space and limit your apps to suit the resources.

You do want to make sure that there is some extra RAM for the disk cache, otherwise performance can become horrible.

I seem to recall that there are some programs that won't run without VM, but I have no idea what they were

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.