Re: Task Manager Process Counters
- From: "Ara Avanesyan" <araav_at_hitegrity_dot_hylink_dot_am>
- Date: Fri, 25 Aug 2006 12:58:24 +0500
"Kh_Oleg" <KhOleg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FA01BF26-735A-4078-9EEB-946C3DB6BC3D@xxxxxxxxxxxxxxxx
Please, enlighten me, if anyone can, regarding the two process counters inof
Windows Task Manager - Mem Usage and VM Size.
As noticed in Task Manager Help and MSDN article, VM Size is "the amount
virtual memory, or address space, committed to a process." Mem Usage, inset
turn, is
"the current working set of a process in kilobytes. The current working
is the number of pages, currently resident in memory."least
So, it is reasonable to suppose that VM Size should be a superset of Mem
Usage, i.e. VM Size should be always >= Mem Usage. But very often, at
for a half of processes, currently running on my machine, VM Size is less
than Mem Usage.
How it is possible?
Oleg.
yeah, quite weired:) actually Task manager's VM Size is not the amount of
virtual memory at all, it corresponds to process' private bytes. dunno if
it's a bug or a feature of taskman:)
__
Thanks,
Ara
.
- Prev by Date: Re: How to change process memory quotas
- Next by Date: Create Thread problem
- Previous by thread: Re: SetConsoleCtrlHandler
- Next by thread: Re: Task Manager Process Counters
- Index(es):
Relevant Pages
|
