March 3, 2008 at 3:27 pm
Need some help to find the reason for 100% Paging File:%Usage Peak value.
My system: Sql Server 2005 (64 bit) Enterprise Edition on MS Windows Server 2003 R2 (Standard x64 Edition) with 16 GB of RAM (14.5 GB is assigned to Sql Server- permanently in use is around 5 GB as I can see from PerfMon). Other performance characteristics are OK (it seems to me)-
CPU < 30, Paging File:%Usage <50, Disk Queue Length, etc. Server is configured with 4GB paging file size (Virtual Memory). What else should I check to find the reason for 100%Usage Peak? Probably it’s tough to say as I read some info from MS that did not help a lot. But anyhow?! Thanks
March 3, 2008 at 6:54 pm
Yuri, why is the page file only set at 4 GB?
It seems as though the OS is starved for memory at times (causing the 100% spikes). SQL may only be using 5 GB but has another 9 GB reserved. OS has < 2 GB left.
Up the page file size, and since SQL seems to only be using 5 GB, return some of that back to the OS.
dab
March 3, 2008 at 7:52 pm
Thanks Doug for your response.:)
Frankly I have no idea why page file size is 4GB (I inherited this server). But I know for a fact that my another similar Sql Server has 2 GB page file size and there is no problem (but certainly it depends ...). My 1-st Sql Server I asked about hosts company Report Server in addition- this can be probably the reason. I mean that 1.5 GB memory left for Windows and applications is not enough as you mentioned.
OK, what should I do now?
Probably, first, to lower Sql Server allocated memory, let say till 10 GB (i.e. for OS and the rest will go 6 GB), and second, to increase page file size from 4 GB to let say 6-8 GB?
Something like this? Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply