Important CPU metrics to look at when troubleshooting CPU performance in VMware environments.
%Ready (%RDY)
•% time a vCPU was ready to be scheduled on a physical processor but couldn’t due to processor contention
•Investigation Threshold: 10% per vCPU
%Co-Stop (%CSTP)
•% time a vCPU in an SMP virtual machine is “stopped” from executing, so that another vCPU in the same virtual machine could be run to “catch-up” and make sure the skew between the two virtual processors doesn’t grow too large
•Investigation Threshold: 3%
%Max Limited (%MLMTD)
•% time the VM was ready to run but wasn’t scheduled because it would violate the CPU Limit set.
•Investigation Threshold: 0%
These values can be obtained using esxtop. See http://www.yellow-bricks.com/esxtop/ for an in-depth explanation.
§Ready (%RDY)
•% time a vCPU was ready to be scheduled on a physical processor but couldn’t due to processor contention
•Investigation Threshold: 10% per vCPU
§Co-Stop (%CSTP)
•% time a vCPU in an SMP virtual machine is “stopped” from executing, so that another vCPU in the same virtual machine could be run to “catch-up” and make sure the skew between the two virtual processors doesn’t grow too large
•Investigation Threshold: 3%
§Max Limited (%MLMTD)
•% time the VM was ready to run but wasn’t scheduled because it would violate the CPU Limit set.
•Investigation Threshold: 0%