Performance Charts do not limit percent values to 100%.
book
Article ID: 312024
calendar_today
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
This article documents a change in behavior from 7.x to 8.x in the UI where it displays the actual used% as opposed to capping the used% at 100.
Customers have reported: "observing high cpu utilization on a nozomi vm appliance on vc while on appliance a different utilization"
Environment
VMware vSphere ESXi 7.x, 8.x
Cause
It is possible for CPU usage and VM usage to be over 100%, due to turbo boost. For VM usage, it can also go above 100% (assuming based on the total number of vCPUs) because of the CPU from IO threads. Due to this, it removes the unnecessary artificial limits on some of the counters ("cpu.usage" and "cpu.usagemhz" are based on "cpu.used", which effectively is already measured in TCs (timer cycles) on VMkernel level, which means that for higher core frequency we are going to receive more TCs (in microseconds) for the same time-interval).
VMs CPU load graph can exceed 100% which was previously limited to 100%. When VMs CPU usage exceeds 100%, performance graphs no longer show CPU usage in percentage - vCenter UI > VM performance in vCenter > VM > Monitor > Performance. Receiving alerts about high CPU usage in VMs and ESXi hosts.
Resolution
As of vSphere 8.0 U3, the percentage value should adjust to match the maximum usage over 100% in the graph.
You may also use the virtual machine > monitor > performance > advanced to see the correct CPU usage of the virtual machine. This graph includes the 16 cores and not 8 vCPU's.
Since performance charts now accurately reflect CPU usage exceeding 100% (due to features like Turbo Boost), administrators should review and adjust any existing CPU utilization alarm thresholds set on VMs or ESXi hosts. If a VM is consistently running above 100% but operating normally, thresholds should be raised accordingly (Consider thresholds above 100% (for example 120 – 150%) or alerts based on sustained usage over time.) to prevent "false alarms" caused by the new, higher metric reporting.
Additional Information
An example of the Alarm Triggered in the vCenter with the CPU Utilization
---
Some users have reported that the MHz on the right of the Overview graph might incorrectly show the same number for the Percentage (%) on the left side as displayed on the right side for MHz.