Re: available memory from task manager

Thanks Pavel,


Three more comments,

1.

Seems you mean there is something wrong with the below calculation of the
article? So, you think the 35M page file is not correct?


No it's not correct. There is no way to calculate the amount of
data in the pagefile from the supplied variables, even approximately.

It is good that we both agree that the calculation from the article 35M is
not correct. Actually, almost all of my confusion comes from the article.

2.

Other things are
reflected in the commit charge but do not occupy either
physical memory or pagefile space (for example, VirtualAlloc'ed
pages that have not been accessed).

Do you mean the demand for zero case? :-)

3.

"Paging File\% Usage" perf counter can be used for this.

There is another way.

http://msdn2.microsoft.com/en-us/library/aa366586.aspx


regards,
George

"Pavel Lebedinsky [MSFT]" wrote:

A quick question, since I am using Windows Server 2003
(Vista is good, but I am not using it in this application), and
the PF value means physical memory + paged file, right?

Not quite. As I mentioned before, PF Usage is actually the
system commit charge. Some things occupy physical memory
but are not reflected in the commit charge (for example,
pages backed by memory mapped files). Other things are
reflected in the commit charge but do not occupy either
physical memory or pagefile space (for example, VirtualAlloc'ed
pages that have not been accessed).

So, we need to use the way the article mentioned to
calculate the size of page file itself, as there is no direct data in task
manager. Are there any other straightforward ways to calculate page file
itself?

"Paging File\% Usage" perf counter can be used for this.

Seems you mean there is something wrong with the below calculation of the
article? So, you think the 35M page file is not correct?


No it's not correct. There is no way to calculate the amount of
data in the pagefile from the supplied variables, even approximately.

--
This posting is provided "AS IS" with no warranties, and confers no
rights.



.

Relevant Pages

  • Re: available memory from task manager
    ... physical memory or pagefile space (for example, ... Do you mean the demand for zero case? ... you can substitute it with "commit charge". ...
    (microsoft.public.win32.programmer.kernel)
  • Re: available memory from task manager
    ... the PF value means physical memory + paged file, ... but are not reflected in the commit charge (for example, ... physical memory or pagefile space (for example, ... calculate the size of page file itself, as there is no direct data in task ...
    (microsoft.public.win32.programmer.kernel)
  • Re: "ideal" paging file size
    ... >> also adjust the amount of Windows paging file size. ... >> Some people say using 1.5X of physical memory is not good for larger ... > swapfile on a separate data hard drive on a separate controller on the ...
    (microsoft.public.windowsxp.general)
  • Re: System cleaning
    ... have a substantial amount of visual documents, ... Windows Directory C:\WINDOWS ... Total Physical Memory 1,024.00 MB ... Available Physical Memory 292.09 MB ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Whats the overhead of sparse files?
    ... The available physical memory before the test was 1,412,960 KB. ... memory was 248,784 KB and the total commit charge was 2,375,996 KB. ... At this point there was 11 GB disk space available. ... I did see it consume up to 27 GB ...
    (microsoft.public.win32.programmer.kernel)
Quantcast