Identifying commit charge peak memory
Posted on 2014-10-08
I am using this article to identify correct page file usage. It references the below but I am unsure on 2008 server where I get the commit charge peak number from. The server is non R2
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.