nerdexam
Broadcom-VMware

2V0-622D · Question #35

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. %RDY in ESXTOP measures the percentage of time a vCPU was ready to run but was waiting for a physical CPU, making it the primary indicator of CPU scheduling contention and VM performance degradation.

Section 7 – Administer and Analyze vSphere 6.5 Performance

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

(58 responses)
  • A
    72% (42)
  • B
    14% (8)
  • C
    9% (5)
  • D
    5% (3)

Why each option

%RDY in ESXTOP measures the percentage of time a vCPU was ready to run but was waiting for a physical CPU, making it the primary indicator of CPU scheduling contention and VM performance degradation.

A%RDYCorrect

%RDY (Ready) directly reflects CPU contention - a consistently high value (above ~10%) indicates the VM is being starved of physical CPU time by the ESXi scheduler, which is the leading ESXTOP indicator for VM performance issues unrelated to hyperthreading.

B%IDLE

%IDLE shows how much time the vCPU spent doing nothing, which reflects low demand rather than a performance problem caused by resource contention.

C%RUN

%RUN shows actual execution time on a physical CPU and indicates utilization, but does not reveal scheduling delays or contention that cause performance degradation.

DCORE UTIL(%)

CORE UTIL(%) measures physical core utilization and is specifically meaningful in hyperthreading contexts; since hyperthreading is disabled on this host, this metric provides little actionable insight.

Concept tested: ESXTOP CPU ready metric for VM performance troubleshooting

Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-A0B2A7B8-4FC5-4B6A-8FE3-7CB7B0F1C4A2.html

Topics

#ESXTOP#CPU ready#VM performance#hyperthreading

Community Discussion

No community discussion yet for this question.

Full 2V0-622D Practice