Should I Disable the Page File if My Computer Has a Lot of RAM?

should-i-disable-the-page-file-if-my-computer-has a-lot-of-ram-00

If you have a computer with a hefty amount of RAM, would you gain any benefits from disabling the page file or should you just leave well enough alone? Today’s SuperUser Q&A discusses the topic to help satisfy a reader’s curiosity.

Today’s Question & Answer session comes to us courtesy of SuperUser—a subdivision of Stack Exchange, a community-driven grouping of Q&A web sites.

Photo courtesy of Collin Anderson (Flickr).

The Question

SuperUser reader user1306322 wants to know if there are any benefits to disabling the page file if a person’s computer has a lot of RAM:

Imagine that I have tons of RAM, say 64 GB, for example. That is a lot, even for gaming computers. Now the default location of a page file in Windows is on the main operating system drive (be it HDD or SSD), which is faster in general but still not as fast as RAM.

Something tells me that disabling the page file on the hard-drive or creating a virtual RAM drive and letting the page file be there could make Windows move all its virtual memory to RAM and increase the system’s performance. But I am not very knowledgeable in that area, so that might not be true at all.

I tried both, but I could not analyze the results to reach a definite conclusion with my knowledge level in memory-related matters. Would this work? If not, then why?

Would user1306322 gain any benefits from disabling the page file?

The Answer

SuperUser contributor David Schwartz has the answer for us:

No matter how much RAM you have, you want the system to be able to use it efficiently. Not having a page file at all forces the operating system to use RAM inefficiently for two reasons:

  • First, it cannot make pages discardable, even if they have not been accessed or modified in a very long time, which forces the disk cache to be smaller.
  • Second, it has to reserve physical RAM to back allocations that are very unlikely to ever require it (for example, a private, modifiable file mapping), leading to a case where you can have plenty of free physical RAM and yet allocations are refused to avoid over-committing.

Consider, for example, if a program makes a writable, private memory mapping of a 4 GB file. The operating system has to reserve 4 GB of RAM for this mapping because the program could conceivably modify every byte and there is no place but RAM to store it. So from the start, 4 GB of RAM is basically wasted (it can be used to cache clean disk pages, but that is about it).

You need to have a page file if you want to get the most out of your RAM, even if it is never used. It acts as an insurance policy that allows the operating system to actually use the RAM it has, rather than having to reserve it for possibilities that are extraordinarily unlikely.

The people who designed your operating system’s behavior are not fools. Having a page file gives the operating system more choices, and it will not make bad ones.

There is no point in trying to put a page file in RAM. And if you have lots of RAM, the page file is very unlikely to be used (it just needs to be there), so it does not particularly matter how fast the device it is on is.

Make sure to check out the lively discussion thread about the topic via the link below!

Have something to add to the explanation? Sound off in the comments. Want to read more answers from other tech-savvy Stack Exchange users? Check out the full discussion thread here.

Akemi Iwaya is a devoted Mozilla Firefox user who enjoys working with multiple browsers and occasionally dabbling with Linux. She also loves reading fantasy and sci-fi stories as well as playing "old school" role-playing games. You can visit her on Twitter and .