That NUMA and vNUMA question
Posted on 2016-11-10
This question is based on settings to for NUMA and vNUMA and what is the best way to set Cores Per Sockets and Virtual Sockets in the VM settings.
So, when enabled vNUMA exposes the VM OS to the physical NUMA.
But is it automatically set?
By default, if I recall, VMware recommends setting Core Per socket to 1 and changing Virtual Sockets thus vNUMA will be enabled to select the best NUMA configuration to be used?
So, with that said, we have a requirement to test customer software on systems with multiple CPUs and various amounts or RAM.
Our ESXi host has 2 cpu sockets, 8 cores, and 32 Logical processors with 512 GB of RAM.
I logged onto the ESXi host and see that there are 2 NUMA Nodes available.
VM requirements :
Win7 Vm with 2 vCPUs
Win7 Vm with 4 vCPUs
Win7 Vm with 8 vCPUs
Centos Server with 4 vCPUs
Centos Server with 8 vCPUs
Centos Server with 16 vCPUs
One test VM that is Centos Server, we initially have set as 4 Core Per Sockets and 2 Virtual Sockets giving 8 vCPUS.. If I understood the above info I stated, this would not enable vNUMA? Is this still a valid set up for vCPUs?
So, should we set the VMs vCPUS as:
1 Core Per Socket and 8 Virtual Cores,
1 Core Per Socket and 16 Virtual Cores,
Stay with something like
4 Core Per Sockets and 2 Virtual Cores, etc?