Question Locked

Q about a TechRepublic article

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

the article is "Decipher Task Manager's page file usage data".
(by Greg Shultz)

http://articles.techrepublic.com.com/5100-10878_11-5071997.html

i found it very interesting,

but i just couldn't understand something very profound there.it says:
"you can come up with a rough estimate of the actual size of the page file by subtracting the Total Commit Charge from the Available Physical Memory"

i think,shouldn't we subtract the occupied physical memory(total-available) from the commit charge to get the current usage of the page file?
and the logic behind that is:
the commit has the physical and the page file,
if we subtract from it the the physical we get the page file.

3 replies

by tintoman

For example if your total installed memory is 2046Mb and you subtract that from a commit charge of say 1500Mb that would leave you -500 in other words more memory committed than you actually have fitted = otherwise known as a frozen or crashed system

by firefox3

the example you just gave is not possible.
the commit charge holds only the physical memory that is used(plus the page file that is used).

if for say we use all the 2046MB, the commit charge can't be less than 2046MB.

This discussion is closed to new replies.