NCP-EUC · Question #24
Users are reporting that their desktops are running slower than expected in an ESXi-based Nutanix cluster. upon investigation, an administrator determines that desktops on one host are running…
The correct answer is B. High Performance host power policy is disabled. CPU Ready time measures how long a virtual machine's vCPU had to wait before being scheduled on a physical CPU. When the ESXi host power policy is not set to High Performance (B) - for example, if it is set to Balanced or Power Saver - the host's CPU cores may be running at…
Question
Users are reporting that their desktops are running slower than expected in an ESXi-based Nutanix cluster. upon investigation, an administrator determines that desktops on one host are running slower and have higher CPU Ready times than on other hosts. What is causing this issue?
Options
- AHigh Performance host power policy is enabled
- BHigh Performance host power policy is disabled
- CInline Compression has been disabled on the desktop storage container
- DErasure coding's increased overhead has caused a slowdown in the environment
How the community answered
(28 responses)- A4% (1)
- B82% (23)
- C11% (3)
- D4% (1)
Explanation
CPU Ready time measures how long a virtual machine's vCPU had to wait before being scheduled on a physical CPU. When the ESXi host power policy is not set to High Performance (B) - for example, if it is set to Balanced or Power Saver - the host's CPU cores may be running at reduced frequencies or sitting in lower power states (C-states). When a VM needs CPU cycles, the host must first ramp up the CPU to full speed, introducing a delay that shows up as CPU Ready time. This explains why desktops on that one host are slower while others are fine: the power policy setting is host-specific. High Performance enabled (A) would actually improve performance, not degrade it. Inline Compression (C) and Erasure Coding (D) are storage-layer features that do not directly cause elevated CPU Ready times.
Topics
Community Discussion
No community discussion yet for this question.