2V0-622 · Question #288
An administrator is investigating virtual machine performance issues using ESXTOP. The ESXi host does not have hyperthreading enabled. Which statistics would be relevant for troubleshooting VM perform
The correct answer is A. %RDY. In ESXTOP, %RDY (Ready) directly measures CPU scheduling contention, making it the primary indicator of VM performance problems on a host without hyperthreading.
Question
An administrator is investigating virtual machine performance issues using ESXTOP. The ESXi host does not have hyperthreading enabled. Which statistics would be relevant for troubleshooting VM performance issues?
Options
- A%RDY
- B%IDLE
- C%RUN
- DCORE UTIL(%)
How the community answered
(48 responses)- A77% (37)
- B13% (6)
- C6% (3)
- D4% (2)
Why each option
In ESXTOP, %RDY (Ready) directly measures CPU scheduling contention, making it the primary indicator of VM performance problems on a host without hyperthreading.
%RDY represents the percentage of time a vCPU was ready to run but was waiting to be scheduled on a physical CPU core. Elevated %RDY values indicate that the ESXi host cannot satisfy the VM's CPU demand quickly enough, which manifests as degraded application performance inside the guest.
%IDLE reflects how much time vCPUs spent doing nothing, indicating the VM is underutilizing CPU resources rather than experiencing a bottleneck.
%RUN shows time the vCPU spent actively executing on a physical CPU and does not reveal contention or scheduling delays that degrade performance.
CORE UTIL(%) measures utilization across both logical processors of a hyperthreaded core and is only meaningful and relevant when hyperthreading is enabled on the host.
Concept tested: ESXTOP %RDY metric for CPU scheduling contention
Source: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-monitoring-performance/GUID-6F30A9EC-11A5-4E34-BF83-1BE83CBBC857.html
Topics
Community Discussion
No community discussion yet for this question.