Win 7 64 bit Pagefile tweaks

BlackDeath

Distinguished
Dec 12, 2009
33
0
18,540
Know I have done a good amount of research and heard all different angles. I am going to test some of these things myself and time it real time with a stop watch! This tweak is mostly aimed at system performance for gaming but would like to hear the pro's and cons.

Win 7 64x I have a Core i5 750 overclocked to 4Ghz and I have 8GB DDR3 1600, GTX 570 and a Velociraptor 300GB 10k RPM drive. So my system moves fast as it is.

I was wondering if someone from Toms Hardware could do a definitve test showing the performance ganes and ideal setups.

System ram (hardware) is much faster then a pagefile on any hard drive. Some programs want to have a pagefile but most seem to be like Adobe Photoshop.

I have seen people say over 4GB disable page file.
Set page file to 512MB with over 4GB of RAM.
Setup pagefile on 2nd hard drive.
Leave it to system managed on Win 7 because it handles it differently then WinXP used to and any tweaks make no difference.

So again I can do my own personal testing but I think it would be great to have a full review to answer all these questions and put it to bed so to speak. I honestly think it would be very benificial to do an article then have information just posted in the forums. What do you think guys?

 
Solution
^+1

There isn't any question that having enough RAM to be able to eliminate the pagefile altogether is your very best performance option. No pagefile, regardless of what kind of device it's on, is as fast as simply having the program resident in memory. This is because any page that isn't in memory incurs a pagefault interrupt followed by thousands of instructions to find a free memory page, "read" the required page back into memory, and then update the memory mapping unit. When the choice is between simply executing a RAM-resident instruction vs. executing thousands of OS instructions to do the reading/remapping, there really isn't any question as to which is faster.

There aren't any modern programs I'm aware of that require a...
Well, the answer is always going to be "It depends." It depends on which applications you are running and how much memory they use in the aggregate. Some even create their own scratch files to avoid paging system memory; I have mixed feelings about that approach.

We-all can't even agree on whether Win7 should have a pagefile, and whether it should be on your SSD or not. I personally have a pagefile on my SSD, but that's a personal choice.

What I would do (did do at work) is run a full workload with the Task Manager running. If you see pagefile use, then you need your pagefile. My current PF usage is 1 GB, with the Commit Charge peak value a little over. Since my memory is 2 GB (!), I'm not paging at the moment.

The reason that there isn't a "full review" is that the answer is so dependent on what apps you are running. If you've done a good amount of research and read various opinions on the subject here in the forums, you have as much information as you are going to get for the general answer.
 
^+1

There isn't any question that having enough RAM to be able to eliminate the pagefile altogether is your very best performance option. No pagefile, regardless of what kind of device it's on, is as fast as simply having the program resident in memory. This is because any page that isn't in memory incurs a pagefault interrupt followed by thousands of instructions to find a free memory page, "read" the required page back into memory, and then update the memory mapping unit. When the choice is between simply executing a RAM-resident instruction vs. executing thousands of OS instructions to do the reading/remapping, there really isn't any question as to which is faster.

There aren't any modern programs I'm aware of that require a pagefile to be present. The last version of Photoshop I used that required a pagefile was Photoshop 6. I've been running my system without a pagefile for two years now and I've never encountered any issues whatsoever.

But whether or not you CAN disable the pagefile depends entirely on what kind of programs you run, how many of them you run at the same time, and what kind of documents/files you open with those programs. Everyone is different - it's not possible (and is indeed dangerous) to give a general rule, because it inevitably won't work for some people.

What you need to do is to load up as many programs as you ever run at once, use them to open up as many of the biggest documents / files / whatever that you ever work with at once, and actually see how much memory you're using. If you're using less than whatever your RAM size is after allowing for a safety margin, then you can probably get away with disabling the pagefile.
 
Solution



There is one possible "error" with the load-all-programs-approach and that is (from my observations) that the memory usage will be different if there is a pagefile present. Somewhere around 85% of physical memory usage some algorithm in the memory manager subsystem will kick in and start to page out to the swap file.

Since this is hard to see from ordinary Taskmgr it could seem like you have more RAM available than there really is when the swapping has taken place. You would have to combine with Perfmon to see the actual pagefile usage. Link how to do this: http://rickardnobel.se/archives/89

Perhaps the best way is to actually test with pagefile, do the load all programs, "feel" the responsiveness of the system and then disable the pagefile and try again.


 
Thank you for your answers as they all pretty much echo what I have seen throughout many different web pages. I am continuing to try different combinations and see what works best for me. Hopefully it will answer other peoples questions in a centralized location here on Toms Hardware :)
 
_________________________________________________________________________

Instead of disabling the pagefile altogether, you could opt to load Windows into RAM by modifying your registry. This make Windows perform faster and still leaves your pagefile intact for applications that require it. Load Windows into RAM by doing the following steps:

With Administrator rights, go to Start>Run. Type ‘Regedit‘ and hit enter.

In the registry editor go to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager\Memory Management\DisablePagingExecutive

Double click the DisablePagingExecutive and change the value to “1“.

(If DisablePagingExecutive doesn't exist, you may create it yourself and assign it a value of '1'.)