The page file should be one and one-half the size of RAM!
The system should manage the size of RAM!
It is 2014, who needs a page file!
You may hear any of the above from colleagues or clients in today's day and age. The long and short of it is that you cannot easily and accurately compute the the needed page file ahead of time in many environments due to different software that is used. Below you will find some references as well as an excerpt from a write up I wrote a couple years ago for sizing virtual memory in a specific environment.
Pushing the Limits of Windows: Virtual Memory (really the be-all guide)
How to use the DedicatedDumpFile registry value to overcome space limitations on the system drive when capturing a system memory dump (I used this on the 2012 build to eliminate the tie between dumps and PF)
How To Size Page Files on Windows Systems (good reference)
The Pagefile Done Right! (my go-to guide)
PAGE FILE SIZING
“Perhaps one of the most commonly asked questions related to virtual memory is, how big should I make the paging file? There’s no end of ridiculous advice out on the web and in the newsstand magazines that cover Windows, and even Microsoft has published misleading recommendations.” –Mark Russinovich
The following items hold true in regards to the Windows Page File.
1. Even systems with large amounts of RAM benefit from the presence of a page file.
2. The page file space is no longer needed to capture a full system dump as it was on legacy systems. (http://blogs.msdn.com/b/
3. There is a performance hit to a system whenever the operating system automatically resizes the page file.
4. Excessive use of the page file will result in poor system performance as the speed of disk is much slower than that of RAM.
5. Never stripe paging files (you can have more than one) across multiple volumes on the same physical disk. This can lead to performance issues.
6. Splitting a page file across multiple physical disks will increase performance.
7. “To optimally size your paging file you should start all the applications you run at the same time, load typical data sets, and then note the commit charge peak (or look at this value after a period of time where you know maximum load was attained). Set the paging file minimum to be that value minus the amount of RAM in your system (if the value is negative, pick a minimum size to permit the kind of crash dump you are configured for). If you want to have some breathing room for potentially large commit demands, set the maximum to double that number.” –Mark Russinovich
Understanding Virtual Memory:
http://technet.microsoft.com/
(Not for the timid) http://blogs.technet.com/b/
http://technet.microsoft.com/
(Not for the timid) http://blogs.technet.com/b/
No comments:
Post a Comment