2V0-622 · 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 on a 2-node NUMA host suffers remote memory access penalties when vCPUs and memory span nodes; explicitly distributing vCPUs and enabling automatic memory affinity restores NUMA locality.
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
(45 responses)- A38% (17)
- B44% (20)
- D18% (8)
Why each option
A 4-vCPU VM on a 2-node NUMA host suffers remote memory access penalties when vCPUs and memory span nodes; explicitly distributing vCPUs and enabling automatic memory affinity restores NUMA locality.
Numa.PageMigEnable controls proactive page migration between nodes for memory balancing, but alone it does not address the scheduling imbalance causing the observed CPU performance problem.
Numa.AutoMemAffinity instructs the VMkernel to automatically migrate the VM's memory pages to the NUMA node where its vCPUs are currently scheduled, reducing costly cross-node memory access latency.
Setting CPU affinity to pin 2 vCPUs to each NUMA node ensures the VM's workload is explicitly balanced across both nodes, preventing all vCPUs from being co-scheduled on a single overloaded node while also enabling the memory scheduler to align memory with local vCPUs.
Binding all 4 vCPUs to a single NUMA node concentrates the entire workload on one node, squandering the second node's CPU resources and potentially worsening contention on that node rather than alleviating it.
Concept tested: NUMA CPU affinity and memory locality optimization for VMs
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-BBF15066-9125-4D1B-AAC2-8F6B5CC20B2E.html
Topics
Community Discussion
No community discussion yet for this question.