NUMA identification

For the best performance, avoid using resources in different NUMA nodes for a single VM.

The following shows CPU to NUMA mapping:

[root@esxi-tiger-14-7:~] for X in 0 1; do echo -n "NUMA${X}: "; cpuList=`vsish -e ls /hardware/numa/${X}/pcpus`; echo $cpuList; done
NUMA0: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
NUMA1: 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35

The following shows NIC to NUMA mapping:

[root@esxi-tiger-14-7:~] vsish -e cat /net/pNics/vmnic4/properties | grep NUMA
   Device NUMA Node:0

The memory that ESXi uses is automatically optimized for NUMA. Do the following to see the memory installed:

[root@esxi-tiger-14-7:~] esxcli hardware memory get
   Physical Memory: 204678979584 Bytes
   Reliable Memory: 0 Bytes
   NUMA Node Count: 2

With a sane hardware build, the assumption is that the memory is split equally between NUMAs.