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 Wait counter reflects time a vCPU spent waiting for I/O or swap activity, not CPU scheduling contention from over-commitment.

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 from over-commitment. High Ready values confirm that the ESXi scheduler cannot satisfy demand.

Core Utilization shows the physical core usage percentage but does not directly indicate scheduling latency or contention experienced by individual VMs.

The Co-Stop counter measures the percentage of time a vCPU was placed in a ready state waiting for other vCPUs in the same SMP VM to be co-scheduled simultaneously. Elevated Co-Stop values specifically indicate scheduling contention caused by having too many vCPUs assigned relative to available physical cores.