My statement is completely true.
Here are some facts, as reported right now on my own computer:
PF Usage: 476 mb
Actual physical size of the paging file (pagefile.sys) = 80 mb
Actual active memory content currently in the paging file = 36 mb
(The computer has 1 gb of RAM, pagefile settings are 80 mb minimum and
1 gb maximum).
You will have to admit that it is somewhat difficult to actually use
473 mb of disk space in a file that is only 80 mb in size.
Now here is the explanation as to why PFUsage is not an accurate
indicator of the actual amount of memory paging activity that is
occurring on the computer.
By design, Windows must assign memory address space to satisfy the
full amount of all memory allocation requests that are issued by
Windows components, application programs, and device drivers. And
almost always these allocation requests are for more memory that is
actually needed under normal circumstances. So what Windows does is
to allocate addresses in RAM only to those portions of the requests
that are actually being used, and to allocate addresses in the
paging/swap file to the unused portions. So when I look at the data
I listed at the top of this reply I can tell that there is 440 mb
(=476 - 36) of "phantom" PF Usage, representing the cumulative total
of the memory allocations that have been requested but never actually
used.
In Windows XP this mapping of unused portions to the paging file can
even be done to *potential* space in the paging file, that is space
which could be added to the paging file without exceeding the
allowable maximum size.
Hope this explains the situation.
Good luck
Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair
"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."