Someone asked me about Hyper-V resource utilization. One can assign up-to 4 virtual processors (VP) or vCPU per VM in Hyper-V 2008. And this VM suffered from unacceptably slow performance due to high CPU utilization. There were only a couple of VMs running per host. If he were to add more CPU cores to the parent host, would performance improve?
The answer is most probably not unless you've already over-packed the host with many VMs. Even if the host parent have many more CPU cores, it couldn't assign more than 1 physical CPU core to 1 VP. Although Microsoft uses the term "Logical Processor" (LP) instead of CPU core, it's an open secret that one LP represents one CPU core.
Each node is running 3 VMs (terminal servers) or total 9 VMs for the entire Hyper-V cluster. The CPU utilization of each VM is averaging 95-100% and many users have complained of slowness in performance. However, the CPU utilization of each parent host is only 50% for each host. In other words, all the VMs are only utilizing half of the 4 x 6 CPU cores per host, even though each VM is nearly saturated.
This is the “math”:
1) Total no. of nodes in cluster = 3
2) No. of logical processors (LP) per node = 4 x 6 CPU cores = 24
3) Ratio of virtual CPU (vCPU) to LP (for best performance) = 1:1
4) Max no. of vCPU per VM = 4
5) No. of terminal server VMs per node = 3
6) Current CPU resource utilized by all VMs per node = 4 x 3 = 12 LPs
Based on above, we calculated that our current CPU utilized by Hyper-V is just 50% per node.
Unused utilization = max no. of LP per node – utilized LP per node = 24 - 12 = 12 (or 50%). When we checked the resource monitor on each parent host, it is indeed the number. A further check with Microsoft support confirms this understanding.
Hence, my recommendation to that someone is to
1) assign more VMs per host, so that more CPU resource can be utilized; or
2) upgrade the Hyper-V hosts to Windows Server 2012 where up-to 64 vCPU can be assigned to each VM
No comments:
Post a Comment