RE: Virtual memory and page file for performance - Help!
- From: jetan@xxxxxxxxxxxxxxxxxxxx ("Jeffrey Tan[MSFT]")
- Date: Tue, 29 Aug 2006 06:16:30 GMT
Hi Sharon,
Sorry for letting you wait.
I see that every process still uses theI assume you are talking about "VM Size" column in Task Manager "Processes"
virtual memory (shown on the Task Manager).
tabpage.
Actually, this column does not mean virtual memory usage of a process, but
it equals "Process: Private Bytes" in performance monitor, which means the
current size, in bytes, of memory that this process has allocated that
cannot be shared with other processes. So this value does not mean that you
are using pagefile.
Also, "Mem Usage" column equals "Process: Working Set" in performance
monitor, which means the working set size of the a process.
Based on my test on a WinXP SP2 machine, after I set the pagefile to "No
paging file" in *Advanced* dialog in "System Properties" dialog and clicked
OK, I rebooted the Windows.
After rebooting, in "Advanced" tabpage, I can see that:
"Total paging file size for all drives: 0MB"
I originally thought that the "PF usage" in "Performance" tabpage of Task
Manager will show the true pagefile usage.
However, in I found that "PF usage" value will not be 0 after rebooting,
but still >90M. By opening some new applications, this value will increase
above 200M. So it seems that pagefile is not disabled at all.
By discussing this issue with our kernel team, I was told that "PF usage"
value actually equals to "Memory\Committed Bytes" in performance monitor,
which is the system-wide commit charge of memory. So this is expected.
In Vista, the performance team has fixed some of the most confusing
terminology in task manager (Mem Usage becames Working Set, VM Size ->
Commit Size etc).
However, "pagefile usage" seems still not be replaced with "commit charge".
Hope this information helps.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Prev by Date: RE: Virtual memory and page file for performance - Help!
- Next by Date: RE: Virtual memory and page file for performance - Help!
- Previous by thread: RE: Virtual memory and page file for performance - Help!
- Next by thread: RE: Virtual memory and page file for performance - Help!
- Index(es):
Relevant Pages
|
Loading