Why not go to the source and ask the horse...
http://support.microsoft.com/kb/555223
Memory, Pages Output/Sec - this shows how many virtual memory pages were
written to the pagefile to free RAM page frames for other purposes each
second.
This is the best counter to monitor if you suspect that paging is
your performance bottleneck. Even if Committed Bytes is greater than the
installed RAM, if Pages Output/sec is low or zero most of the time, there is
not a significant performance problem from not enough RAM.
-----Original Message-----
From: Windows Home/SOHO [mailto:[EMAIL PROTECTED] On Behalf Of
Slattery, Tim - BLS
Sent: Friday, January 12, 2007 10:13 AM
To: [email protected]
Subject: Re: Ram for Win2k
> Page Faults mean that a process wanted some more memory
> allocated to it, possibly it's just asking for more, and
> possibly it wants to access something that was already
> allocated memory, but that has been posted out to the
> pagefile, with the memory re-assigned to another task
Not exactly. A page fault occurs when a process accesses memory that's
been written to the swap file. The OS has to identify a page currently
in memory to be written to the swap file, then read in the needed data
from the swap file.
> If you have multiple tasks showing lots on the Delta at the
> same time, then you may be able to make sufficient use of
> more memory to justify the expense.
Absolutely. More RAM would mean fewer page faults, less reading from and
writing to the disk.
--
Tim Slattery
[EMAIL PROTECTED]
--
----------------------------------------
The WIN-HOME mailing list is powered by L-Soft's renowned
LISTSERV(R) list management software. For more information, go to:
http://www.lsoft.com/LISTSERV-powered.html
