On Thu, May 7, 2009 at 3:50 PM, Christopher Bodnar <[email protected]> wrote: > OK, I’ve got this SQL 2005 server (x64 W2K3) with 64G of memory and I’m > looking at the PF usage # which has me worried: > But if I look at the % Usage of the pagefile in Perfmon it shows only 11%, > which seems good. I also look at Memory Pages Output/sec and it’s always 0, > which is also good.
Right. Task Manager mislabels things for reasons known only to Microsoft. When Task Manager says "PF Usage" it really means "Commit Charge", which has nothing to do with page file usage. > But my Memory committed bytes is ~64G, almost at the > amount of physical memory. I’m wondering why this is not paging more ... MS SQL Server dynamically allocates and releases memory from OS, in response to the load on the system. See: http://support.microsoft.com/kb/321363 So commit charge is high because MS-SQL Server is using most of the RAM on the system, because the system doesn't need it for anything else (you said load was low). The theory is that if one has the RAM, one intends for it to be used, not sitting idle. Not everyone agrees with the particular approach Microsoft uses to address that, and it makes multi-workload tuning kind of complicated, but that's the expected behavior from MS-SQL. If your server (or VM instance) is dedicated to MS-SQL, then it's actually desirable. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
