Would you ever limit page file size on a server?

I've had mixed results.

We give a seperate drive dedicated to page files on all our virtual machines and leave the settings as system managed. However on some very memory intensive app servers I've found performance is increased by setting specific page file settings. For example on the GPS business intelligence servers (2008 R2) which have 8gb memory, system managed page file never appeared to go beyond 6gb and performance on these boxes was poor. I set custom sizes of 10-15gb and the performance is much better.
 
*shrug* I work for a french company, they're probably too busy eating cheese, drinking wine and shrugging at each other to bother giving me a reason why. ;)


LOL that reminds me of one of our clients which is also a French company have pretty similar crazy IT policy's with little response to the reasoning behind them!
 
Like many, we have our page file on a different volume. I've gone with the size of disk being 1.5 x memory, and set the page file to dynamic.

We've done this for a different reason though,
We have our VMWare environment replicated using HP Continuous Access and SRM to another site, and have created the paging file disks on non-replicated storage.
This, in theory, should keep replication to data only, rather than volatile data like the paging file.

Do you not require crash dump file in the event of a BSOD?
 
Back
Top Bottom