Home » VMware » 2V0-622 » Which two Performance Counters should be reviewed in the vSphere Web Client Performance Charts to confirm if there is contention on the host?

Which two Performance Counters should be reviewed in the vSphere Web Client Performance Charts to confirm if there is contention on the host?

10/29/2017 – by Mod_GuideK 1

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.)
A. Wait
B. Ready
C. Core Utilization
D. Co-Stop

SHOW ANSWERS

One thought on “Which two Performance Counters should be reviewed in the vSphere Web Client Performance Charts to confirm if there is contention on the host?”

Returning to Valhalla says:

05/21/2019 at 11:31 AM

READY: The time a virtual machine must wait in a ready-to-run state before it can be scheduled on a CPU
CO-STOP: Amount of time a SMP virtual machine was ready to run, but incurred delay due to co-vCPU scheduling contention.

Reply

One thought on “Which two Performance Counters should be reviewed in the vSphere Web Client Performance Charts to confirm if there is contention on the host?”

Leave a Reply Cancel reply