Do not use Task Manager in Hyper-V for Processor Measurements
I’m doing another blog post about the processor utilization in a Hyper-V environment because it seems like my last blog post on this subject was misinterpreted.
When Ewan Fairweather and I ran a few BizTalk servers as guest computers to 100% CPU. We brought up Task Manager and it showed very little, if any CPU usage. We thought to ourselves that either Hyper-V has the most efficient use of CPU utilization or there is something wrong. It turns out that the host computer (root partition) is considered just another virtual computer running on the hypervisor. This means that the CPU usage we see in Task Manager is only the CPU usage of the host computer only. Therefore, if you want to know how much CPU utilization your physical processors are really getting, then use the “\Hyper-V Hypervisor Logical Processor(*)\% Total Run Time”. The processor resource is the only resource affected in this way – meaning you can measure memory and network using the normal counters.
Read Tony Voellm’s blog (he is the Hyper-V Performance Lead) at:
I was involved in testing performance of Hyper-V in a Microsoft BizTalk Server environment with Ewan Fairweather and we wrote this article:
Always use the Hyper-V Hypervisor performance counters first!