I checked over the details of this feature and I'd say this is smthg that is suited for small VMs (small enough to fit subNuma domain) with low latency requirements. Looks like I always managed to avoid this by using memory interleaving feature. You know i was not aware about this SNC feature on the Intel CPUs Please bear in mind that it has somewhat limited support for more exotic NUMA environments Virtual Machine Compute Optimizer | VMware Flings You may want to check this fling for further results: It looks like you are going into VM that will utilize 3 physical NUMA nodes. If you want to increase the vCPU above 16, you may need to look for amount cores divided by 3. If you have CPU settings manually defined, the vNUMA autosizer does not intervene, and this setting is not usedģ. The default setting seems to be aligned with your physical NUMA size -> 2 CPU * 16 cores / 4 NUMA nodes = 8 coresĢ. If your VM will have 10 cores, then it will have 2 vNUMA nodes and vNUMA autosizer will set it on 2 sockets with 5 cores.ġ. With the default setting = 8, when your VM has 8 cores it will have just 1 vNUMA node and vNUMA autosizer will set your VM on 1 socket with 8 cores. This setting is for defining the minimum number of cores above which vSphere kernel will start to create additional vNUMA nodes Can you explain a bit how come you have four NUMA nodes with just 2 CPUs ?Īs I understand this setting you don't need to change it when you increase the amount of vCPUs.
0 Comments
Leave a Reply. |