Task Manager - Misleading

[Sc4freak]

The performance tab of Windows Task Manager is extremely misleading at best. Treason at worst. The Page File Usage graph DOES NOT indicate how much page file is in use. it indicates how much RAM PLUS Page file is in use. I just realised this. Before, I didn't know what the Commit Charge was. After some reading I discovered that the "Total" was all memory used, whether page file or RAM. "Limit" was the maximum memory avaliable (RAM + Page File) And "Peak" is the most amount of memory used.

Is this correct? Becuase I copied 400mb into memory, I saw the "PF Usage" graph in Task Manager jumped 400mb, and also my Available Physical Memory dropped 400mb. And I spent weeks trying to stop windows from duplicating the file in both the RAM and Page File. Goddamn this Task Manager!


Sorry everyone, I just had to vent.

 

[Nothinman]

The performance tab of Windows Task Manager is extremely misleading at best.

Most things in Windows are misleading.

s this correct?

Not really, mainly because the numbers you get from task manager are really rough and it's impossible for it to take some things into consideration.

Becuase I copied 400mb into memory, I saw the "PF Usage" graph in Task Manager jumped 400mb, and also my Available Physical Memory dropped 400mb. And I spent weeks trying to stop windows from duplicating the file in both the RAM and Page File

Windows will never duplicate data in the pagefile, if you read a file into memory the backing store for that file will remain the file on disk. That file will never hit the pagefile. It's possible that some of it may make it there because it could have been copied to another memory location and modified by a process, but even then as long as you have enough memory it will only get a pagefile reservation and not actually hit the disk until memory gets low. Luckily pagefile reservations count against whatever taskmgr uses for PF Usage as well, so that makes it an even less reliable gauge.

 

[edmicman]

oh no! what ever will we do?