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

Wait time can indicate a VM is waiting for various resources (e.g., I/O, memory), but it is not as specific a measure of CPU contention or vCPU over-commitment as Ready or Co-Stop time.

CPU Ready Time, or 'Ready', measures the percentage of time a virtual machine is ready to execute but is waiting for its turn to be scheduled on a physical CPU core. High Ready time directly indicates CPU contention and potential vCPU over-commitment.

Core Utilization measures the overall busyness of physical CPU cores, but it doesn't directly reveal if individual virtual machines are experiencing contention due to over-commitment, as a host can be highly utilized without significant VM resource contention.

CPU Co-Stop Time, or 'Co-Stop', specifically measures the time a multi-vCPU virtual machine spends halted, waiting for all its configured vCPUs to be scheduled simultaneously on physical cores. High Co-Stop time is a strong indicator of contention caused by vCPU over-commitment, impacting multi-vCPU VM performance.