High CPU Ready Time Troubleshooting: vCPU Oversubscription
An administrator notices that a critical VM running a database has a high CPU ready time average (over 20%) on a host with 2 physical CPUs (16 cores each). The host is running 6 VMs, each with 8 vCPUs. What is the most likely cause of the high ready time?
Quick Answer
Reducing the vCPU count on some VMs is correct because the math here reveals genuine physical CPU oversubscription: the host has 32 physical cores total, but six VMs each configured with 8 vCPUs add up to 48 vCPUs contending for those same 32 cores. CPU ready time measures how long a VM's vCPU is waiting for the physical scheduler to give it a core, and a sustained average above 20% is a strong signal that the hypervisor simply does not have enough physical cores to go around when all the VMs want to run simultaneously. This differs from CPU usage or utilization metrics, which reflect how busy the cores are once scheduled; ready time instead captures the queuing delay before that scheduling even happens, exactly the symptom a latency-sensitive database VM would suffer from. Lowering the vCPU count on some of the VMs directly reduces the oversubscription ratio, giving the scheduler an easier job and cutting down on the queuing delay. Other fixes like adjusting shares or reservations can reprioritize who gets scheduled first during contention, but they do not reduce the total contention itself the way trimming vCPU counts does. Whenever a question gives you vCPU and physical core counts alongside a high ready time metric, do the arithmetic on the oversubscription ratio first, since that is almost always the root cause being tested.
⚠ Common exam trap
A common mix-up: candidates confuse CPU ready time with memory pressure (Option D) or assume Hyper-Threading is the culprit (Option A), when the core issue is simply an over-provisioned vCPU-to-core ratio.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The host has too many vCPUs relative to physical cores; reduce vCPU count on some VMs.
The host has 32 physical cores (2 CPUs × 16 cores) but the 6 VMs each with 8 vCPUs total 48 vCPUs, resulting in a vCPU-to-core ratio of 1.5:1. A CPU ready time average over 20% indicates severe contention for physical cores, as the hypervisor cannot schedule all vCPUs simultaneously. Reducing the vCPU count on some VMs would lower the ratio and alleviate the scheduling bottleneck.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Hyper-Threading should be disabled to reduce scheduling overhead.
Why it's wrong here
Incorrect: Disabling HT reduces available logical CPUs, worsening the overcommitment.
- ✓
The host has too many vCPUs relative to physical cores; reduce vCPU count on some VMs.
Why this is correct
Correct: vCPU overcommitment leads to high ready time.
- ✗
The VMs are not configured with NUMA awareness.
Why it's wrong here
Incorrect: NUMA awareness helps memory locality but does not directly reduce CPU ready time.
- ✗
Memory overcommitment is causing excessive swapping.
Why it's wrong here
Incorrect: The issue is CPU-related, not memory.
Go deeper
Related to this question
About these practice questions
One of 498 original VCP-DCV practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
5 more ways this is tested on VCP-DCV
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An administrator notices that a critical virtual machine is running slowly. The VM has 8 vCPUs and 32GB memory. The host is an ESXi 7.0 server with two Intel Xeon Gold 6248 sockets (20 cores each, hyperthreading enabled). The VM's CPU ready time is consistently above 10%. What is the most likely cause?
medium- A.The VM's vCPUs are pinned to a single NUMA node causing contention.
- ✓ B.The host has too many VMs running and CPU oversubscription is too high.
- C.The VM is over-provisioned on vCPUs relative to the host's physical cores.
- D.The VM is using Eager Zero Thick disks causing high I/O latency.
Why B: High CPU ready time indicates the VM is ready to run but the hypervisor cannot schedule it. This is typically due to excessive CPU oversubscription. Option B correctly identifies that having too many VMs on the host leads to high CPU contention, causing ready time. Option A is incorrect because pinning vCPUs to a single NUMA node can increase ready time if other nodes are idle, but with only 8 vCPUs on a 40-logical-CPU node, contention is unlikely unless many other VMs are also pinned. Option C is incorrect because over-provisioning refers to total vCPUs exceeding physical CPUs, not individual VM vCPU count; the host has 80 logical CPUs, so 8 vCPUs is not over-provisioned. Option D is incorrect because disk I/O does not cause CPU ready time; it causes disk latency.
Variation 2. During a performance review, an administrator notices that a VM with 4 vCPUs and 16 GB memory is experiencing over 10% CPU ready time. The host has two 8-core sockets (hyper-threading enabled) and 256 GB memory. The host runs 15 other VMs with varying CPU loads. What is the most likely cause?
medium- A.NUMA node mismatch causing cross-node memory access.
- B.CPU hot-add is enabled on the VM.
- C.Memory over-provisioning causing ballooning.
- ✓ D.Over-provisioning of vCPUs on the host leading to contention.
Why D: The host has 16 physical cores (with hyper-threading, 32 logical processors), but running 16 VMs with a total of 4 vCPUs each would require 64 vCPUs. This 2:1 over-provisioning ratio, combined with varying CPU loads, leads to contention for physical CPU resources, manifesting as CPU ready time exceeding 10%. CPU ready time measures the percentage of time a VM is ready to run but waiting for a physical CPU to become available.
Variation 3. Refer to the exhibit. The vSphere administrator observes that vm1 has a %RDY value of 20.5. What is the most likely cause of this high ready time?
hard- A.The VM is experiencing network packet loss
- B.The VM's virtual disk is causing I/O latency
- ✓ C.The host's physical CPUs are overcommitted
- D.Insufficient memory is allocated to vm1
Why C: High %RDY indicates the VM is ready to run but is being queued due to CPU contention. This is typically caused by overcommitment of pCPUs. Memory or storage latency would show in other counters.
Variation 4. An administrator is troubleshooting a virtual machine that experiences intermittent performance issues. The VM is configured with 8 vCPUs and 32 GB memory. The administrator runs esxtop and sees that the %RDY for the VM is consistently above 20%. What does this indicate?
hard- ✓ A.The VM is contending for CPU resources due to overallocation of vCPUs.
- B.The VM's virtual disks are experiencing high latency.
- C.The VM is experiencing memory ballooning.
- D.The VM is using its CPU resources efficiently.
Why A: High %RDY indicates that the VM is ready to run but is waiting for CPU resources, meaning the CPU scheduler cannot allocate physical cores quickly enough. This is typically caused by over-allocation of vCPUs relative to available physical cores, leading to contention. Option A correctly identifies this condition. Option B is incorrect because high %RDY is not related to disk latency; disk latency is measured by other metrics like DAVG/GAVG. Option C is incorrect because memory ballooning is a memory management technique, not directly indicated by %RDY. Option D is incorrect because high %RDY signifies inefficient CPU scheduling, not efficient utilization.
Variation 5. An administrator is troubleshooting a VM that is running slowly. The VM has 4 vCPUs and 16 GB of memory. The host has 2 physical CPUs with 10 cores each, hyper-threading enabled. The administrator runs esxtop and sees that %RDY for the VM is consistently above 15%. Which action would most likely reduce the ready time?
medium- A.Increase the CPU shares for the VM.
- B.Increase the number of vCPUs to 8 to improve parallelism.
- C.Increase the memory allocation to 32 GB.
- ✓ D.Reduce the number of vCPUs to 2 if the workload does not require 4.
Why D: A %RDY value consistently above 15% indicates the VM is ready to run but is waiting for CPU scheduling time on the host. With 4 vCPUs on a host that has 20 logical CPUs (2 sockets × 10 cores × 2 threads), the VM is likely over-provisioned relative to its workload needs, causing co-scheduling contention. Reducing the number of vCPUs to 2 decreases the co-scheduling demands and reduces ready time, as the VM will require fewer physical CPUs to be available simultaneously. Therefore, option D is correct. Increasing CPU shares (option A) would not help if the host is saturated, adding more vCPUs (option B) would worsen contention, and increasing memory (option C) does not address CPU ready time.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This VCP-DCV practice question is part of Courseiva's free VMware certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VCP-DCV exam.