Yeah, like you didn’t know that already. But I am still surprised how version after version something new and good comes up. New features, however small, get added all the time.

In one of the latest few point revisions, Sysinternals guys added something that will help me particularly well – I/O bytes history graph. What you can see on the right is the screen shot of all three interesting graphs while the current version of NTorrent (code name) is running. The I/O bytes is useful in my scenario because I still do not do any caching and would like to know if under normal circumstances it matters or not. Other BitTorrent clients seem to agree that it matters and mostly all implement some kind of caching.

Yes, I know I can probably see the same using some of the performance counters, but more often than not I just need a quick and dirty overview of what’s going on – with memory, processor time, I/O activity and sockets (yes, Process Explorer can even list all the socket connections you have open).

If your app is .NET based, you can also find quite detailed .NET related information for your process. Finally, the bug where a Process Explorer would trigger handle leaks while inspecting .NET processes has been fixed, so you can leave it open all the time.