I often accidentally close Process Explorer when I only want to close one of its dialogs, because I press the ESC key once too often. Quite annoying.
Is there any way to configure Process Explorer to not close when the ESC key is pressed?
I'm debugging a performance issue on an RDS server, and trying to understand the output of the System Information graphs in Process Explorer:
The I/O graph is showing about 40Mb/s total and the Network and Disk graphs are showing much less in aggregate. What other I/O is contributing to the Process I/O graph, is it memory I/O?
I have a server using 10-25% of the CPU time on Hardware Interrupts according to Process Explorer.
How would I go about logging/diagnosing the cause of all these IRQ calls?
The machine is virtual, so I know the physical hardware is not the problem (although could be drivers, etc).
UPDATE: Tried the information from this article: http://msdn.microsoft.com/en-us/library/ms797921.aspx
Regarding using tracelog.exe and tracerpt.exe to capture DPC and ISR events, but when I run the trace it doesn't have any of that information, even with the -dpcisr switch. I get disk and process info in the report but no interrupts... I know interrupts are happening because Process Explorer is still showing them using 6-15% CPU
What is a process handle and what can we know about a running process through the "handle count" property in a task explorer?
This is something that's always bothered me, so I'll ask the Server Fault community.
I love Process Explorer for keeping track of more than just the high-level tasks you get in the Task Manager. But I constantly want to know which of those dozen services hosted in a single process under svchost is making my processor spike.
So... is there any non-intrusive way to find this information out?