Monitoring processes eating up your memory

sonxEr77

Expert Member
Joined
Oct 22, 2006
Messages
1,809
Reaction score
0
Location
around
Alright i know windows tasks manager does this well, isn't there anything better that can even tell you what's keeping the processor more busy at a point in time (excpet by running spyware remover). When my HDD LED is flashing heavily resulting to a slow PC spyware doctor would be the program showing high usage of mem, especially if its busy scanning. I noticed today after startup the HDD LED was busy & spdoc + FF were 1st two with higher mem usage, even though spdoc was not busy scanning....Couldn't tell what was keeping the PC so busy.. I have Core2Duo 1.87Ghz, 1024 mem
 
Alright i know windows tasks manager does this well, isn't there anything better that can even tell you what's keeping the processor more busy at a point in time (excpet by running spyware remover). When my HDD LED is flashing heavily resulting to a slow PC spyware doctor would be the program showing high usage of mem, especially if its busy scanning. I noticed today after startup the HDD LED was busy & spdoc + FF were 1st two with higher mem usage, even though spdoc was not busy scanning....Couldn't tell what was keeping the PC so busy.. I have Core2Duo 1.87Ghz, 1024 mem
Firefox is a horrible memory hog. Download Process Explorer (available from http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExplorer.mspx) It should give you a handle one what's doing what
 
Process Explorer is the one to go for - for per-process CPU utilisation and per-process memory usage.

What it doesn't tell you definitively is the disk throughput per process, ie when the disk light is busy, what's causing it. According to a discussion I had with the author of ProcExp, Mark Russinovich, that's not monitored by windows and not possible to get hold of (without inserting hooks that would slow your system down).

In any case, a lot of the times when the disk light is busy but no application is doing anything obvious, it's because windows itself is messing around with the paging file. Using ProcExp's views of process memory, and finding the processes that are using a lot, helps to spot the troublemakers.
 
Top
Sign up to the MyBroadband newsletter
X