nerdexam
Broadcom-VMware

2V0-622 · Question #171

Refer to the Exhibit. An administrator is troubleshooting a CPU performance related problem for the SlowVM virtual machine. Which three actions should the administrator take to improve CPU performance

The correct answer is B. Decrease the number of vCPUs assigned to SlowVM. C. Power off other VMs running on the same ESXi host. E. Move SlowVM to another ESXi host with more physical CPU resources available.. When an SMP VM exhibits high Co-Stop due to over-assigned vCPUs on a contended host, reducing vCPU count, offloading competing VMs, or migrating to a less loaded host are the correct remediation actions.

Section 7 – Administer and Analyze vSphere 6.5 Performance

Question

Refer to the Exhibit. An administrator is troubleshooting a CPU performance related problem for the SlowVM virtual machine. Which three actions should the administrator take to improve CPU performance for SlowVM? (Choose three.)

Exhibit

2V0-622 question #171 exhibit

Options

  • AIncrease the number of vCPUs assigned to SlowVM.
  • BDecrease the number of vCPUs assigned to SlowVM.
  • CPower off other VMs running on the same ESXi host.
  • DIncrease the CPU limit for SlowVM.
  • EMove SlowVM to another ESXi host with more physical CPU resources available.

How the community answered

(29 responses)
  • A
    38% (11)
  • B
    48% (14)
  • D
    14% (4)

Why each option

When an SMP VM exhibits high Co-Stop due to over-assigned vCPUs on a contended host, reducing vCPU count, offloading competing VMs, or migrating to a less loaded host are the correct remediation actions.

AIncrease the number of vCPUs assigned to SlowVM.

Increasing the number of vCPUs on an already contended host worsens Co-Stop values because it becomes even harder for the scheduler to find enough free physical cores to simultaneously schedule all vCPUs.

BDecrease the number of vCPUs assigned to SlowVM.Correct

Decreasing the number of vCPUs assigned to SlowVM reduces the co-scheduling burden on the ESXi CPU scheduler, lowering Co-Stop time and allowing the VM to be scheduled more frequently on available physical cores.

CPower off other VMs running on the same ESXi host.Correct

Powering off other VMs frees physical CPU resources on the same host, directly reducing contention that causes high Ready and Co-Stop values for SlowVM.

DIncrease the CPU limit for SlowVM.

Increasing the CPU limit would only help if the VM were being throttled by an existing limit; the exhibit indicates the issue is scheduling contention, not a configured resource cap.

EMove SlowVM to another ESXi host with more physical CPU resources available.Correct

Migrating SlowVM via vMotion to an ESXi host with more available physical CPU capacity resolves contention by placing the VM in an environment where the scheduler can more easily satisfy its vCPU demands.

Concept tested: Remediating vSMP Co-Stop and CPU contention in vSphere

Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-1B4A3D87-2EC4-4C87-A309-6837C3FAF1AC.html

Topics

#vCPU sizing#CPU performance#resource migration#esxtop

Community Discussion

No community discussion yet for this question.

Full 2V0-622 Practice