2V0-621 · Question #160
Users are reporting CPU related performance problems on the virtual machine Email-Prod throughout the day. The resource settings for the VM and the ESXi host the VM is running on are shown below: VM:
The correct answer is B. Enable the advanced parameter Numa.AutoMemAffinity. C. Enable CPU affinity to separate 2 vCPUs for each NUMA node.. A 4-vCPU VM spanning a 2-node NUMA host suffers remote memory access latency - distributing vCPUs across NUMA nodes and enabling automatic memory affinity both reduce cross-NUMA overhead.
Question
Users are reporting CPU related performance problems on the virtual machine Email-Prod throughout the day. The resource settings for the VM and the ESXi host the VM is running on are shown below:
VM:
Email-Prod vCPUs: 4 Memory: 96GB ESXi host:
CPU: 2 x 8 Core Processors Memory: 128GB NUMA architecture. 2 Nodes Which two options would alleviate the observed performance problem for Email-Prod? (Choose two.)
Options
- AEnable the advanced parameter Numa.PageMigEnable.
- BEnable the advanced parameter Numa.AutoMemAffinity.
- CEnable CPU affinity to separate 2 vCPUs for each NUMA node.
- DEnable CPU affinity to bind all vCPUs to one NUMA node.
How the community answered
(37 responses)- A27% (10)
- B57% (21)
- D16% (6)
Why each option
A 4-vCPU VM spanning a 2-node NUMA host suffers remote memory access latency - distributing vCPUs across NUMA nodes and enabling automatic memory affinity both reduce cross-NUMA overhead.
Numa.PageMigEnable only controls whether page migration between NUMA nodes is permitted at all - enabling it without configuring memory affinity does not directly optimize placement for this VM's workload.
Numa.AutoMemAffinity instructs the hypervisor to automatically migrate memory pages to the NUMA node local to the executing vCPUs, reducing costly remote memory accesses that occur when the VM spans both NUMA nodes.
Setting CPU affinity to pin 2 vCPUs per NUMA node aligns each set of vCPUs with a local memory domain, allowing each group to access memory from its own NUMA node and avoiding the latency penalty of cross-node memory traffic.
Pinning all 4 vCPUs to a single NUMA node concentrates all memory and CPU pressure on one node, which can increase local contention and does not leverage the capacity of the second node.
Concept tested: NUMA topology optimization for wide multi-vCPU VMs
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-7A6B5D75-0AB3-4E41-9E91-3E69D07E81F0.html
Topics
Community Discussion
No community discussion yet for this question.