nerdexam
Broadcom-VMware

2V0-621 · Question #169

An administrator is concerned about possible vCPU over-commitment for an ESXi 6.x host. Which two Performance Counters should be reviewed in the vSphere Web Client Performance Charts to confirm if the

The correct answer is B. Ready D. Co-Stop. To detect vCPU over-commitment and scheduling contention on an ESXi host, administrators should monitor the Ready and Co-Stop performance counters, as these directly reflect CPU scheduling delays.

Section 7 – Administer and Analyze vSphere 6.x Performance

Question

An administrator is concerned about possible vCPU over-commitment for an ESXi 6.x host. Which two Performance Counters should be reviewed in the vSphere Web Client Performance Charts to confirm if there is contention on the host? (Choose two.)

Options

  • AWait
  • BReady
  • CCore Utilization
  • DCo-Stop

How the community answered

(60 responses)
  • A
    7% (4)
  • B
    90% (54)
  • C
    3% (2)

Why each option

To detect vCPU over-commitment and scheduling contention on an ESXi host, administrators should monitor the Ready and Co-Stop performance counters, as these directly reflect CPU scheduling delays.

AWait

The Wait counter reflects time spent waiting for I/O or swap operations rather than CPU scheduling contention, so it does not indicate vCPU over-commitment.

BReadyCorrect

The Ready counter measures the percentage of time a vCPU was ready to run but could not be scheduled on a physical CPU, which is the primary indicator of CPU contention caused by over-commitment. A sustained Ready value above 10% signals that the host cannot service virtual machines fast enough.

CCore Utilization

Core Utilization shows the percentage of physical core capacity consumed but does not reveal whether virtual machines are experiencing scheduling delays or contention.

DCo-StopCorrect

The Co-Stop counter measures the percentage of time an SMP virtual machine was waiting for all of its vCPUs to be co-scheduled simultaneously, which directly exposes contention caused by having more vCPUs than available physical CPU threads.

Concept tested: ESXi CPU contention performance counters Ready and Co-Stop

Source: https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-671-monitoring-performance-guide.pdf

Topics

#vCPU over-commitment#CPU ready#co-stop#performance counters

Community Discussion

No community discussion yet for this question.

Full 2V0-621 Practice