2V0-620 · Question #3
A user is trying to retrieve objects from a SharePoint server and finds the request is taking an excessive amount of time. An administrator tries to isolate the issue and notes the following…
The correct answer is A. Host Power Management is directly impacting virtual machine performance. Elevated CPU %Ready on a specific host that resolves after vMotion points to a host-level resource constraint - most commonly Host Power Management throttling CPU frequency.
Question
A user is trying to retrieve objects from a SharePoint server and finds the request is taking an excessive amount of time. An administrator tries to isolate the issue and notes the following:
- Application performance is poor when compared to virtual machines on
other hosts.
- Performance improves when the virtual machine is moved to another
host. The virtual machine encounters higher than expected CPU %Ready times. What conclusion can be reached regarding the performance issues for this virtual machine?
Options
- AHost Power Management is directly impacting virtual machine performance.
- BThe virtual machine has a large number of snapshots.
- CThe Path Selection Policy for the storage device is set differently on the affected host.
- DNetwork I/O control is configured for the portgroup.
How the community answered
(31 responses)- A48% (15)
- B32% (10)
- C6% (2)
- D13% (4)
Why each option
Elevated CPU %Ready on a specific host that resolves after vMotion points to a host-level resource constraint - most commonly Host Power Management throttling CPU frequency.
CPU %Ready measures time the VM is waiting for a physical CPU to be scheduled - when power management policies such as Balanced or Low Power mode reduce CPU clock frequency to save energy, the host processes fewer cycles per second, increasing scheduler contention and %Ready times. Because this is a host-level setting, it explains why the issue is isolated to one host and disappears after migrating the VM.
A large number of VM snapshots degrades storage I/O performance due to snapshot delta-file chain reads, but does not directly cause elevated CPU %Ready times.
The Path Selection Policy affects how storage traffic is distributed across HBAs and paths - it impacts storage latency and throughput, not CPU scheduling wait times.
Network I/O Control limits or prioritizes virtual machine network bandwidth and does not influence CPU scheduling or %Ready metrics.
Concept tested: Host Power Management impact on CPU %Ready times
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-DAB86B08-D64D-4C46-8754-5AFAC8B66E5C.html
Topics
Community Discussion
No community discussion yet for this question.