CV0-003 · Question #85
Users are reporting slow performance on a virtual server. An administrator notices that the virtual CPU is at 50%. Which of the following should the administrator check on the host?
The correct answer is B. CPU wait time. When a VM's vCPU appears at only 50% utilization but performance is degraded, the likely cause is that the hypervisor is not scheduling physical CPU time promptly, which is measured as CPU wait time (CPU ready time).
Question
Users are reporting slow performance on a virtual server. An administrator notices that the virtual CPU is at 50%. Which of the following should the administrator check on the host?
Options
- AI/O throttling
- BCPU wait time
- CSwap files
- DMemory ballooning
How the community answered
(33 responses)- A3% (1)
- B82% (27)
- C6% (2)
- D9% (3)
Why each option
When a VM's vCPU appears at only 50% utilization but performance is degraded, the likely cause is that the hypervisor is not scheduling physical CPU time promptly, which is measured as CPU wait time (CPU ready time).
I/O throttling is a disk or network I/O constraint mechanism and would affect storage or network performance, not CPU scheduling latency.
CPU wait time (also called CPU ready time in hypervisor platforms) measures how long a vCPU is ready to run but must wait for a physical CPU core to become available on the host. Even at 50% reported utilization, high CPU wait time indicates that the VM is being starved of physical CPU cycles by the hypervisor scheduler, directly causing the observed slow performance.
Swap files relate to memory overcommitment - when the host runs out of physical RAM and pages to disk - which is a memory issue, not a CPU scheduling problem.
Memory ballooning is a hypervisor technique to reclaim memory from VMs with low memory pressure, which is a memory management concern unrelated to CPU scheduling delays.
Concept tested: Diagnosing hypervisor CPU ready/wait time impact
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-84A6D5EE-8D4C-4B80-8D43-5ACFE76DC5D3.html
Topics
Community Discussion
No community discussion yet for this question.