We have not enabled this feature though this provides lot of flexibility in upgrading the resources. Simple reason is enabling this feature disables NUMA. That brings the second question why should we care about NUMA ?
What is NUMA ?
The best explanation about NUMA is i think on this site.
https://www.exitthefastlane.com/2016/04/vsphere-design-for-numa-architecture.html
In very simple explanation, to design your virtual environment to be NUMA aligned means ensuring that your VMs receive vCPUs and RAM tied to a single physical CPU (pCPU), thus ensuring the memory and pCPU cores they access are directly connected and not accessed via traversal of a CPU interconnect.
A good basic understanding of NUMA can help administrator or solution architect in:
- Right sizing a VM in terms of cpu and memory.
- Avoid potential performance issue on heavy hitter applications running on big size VMs.
- Gently push back on DBA for demanding more resources on DB VMs with logical explantion of benefits of remaining within vNUMA node and more is not always good. ( DBA is just example i took to explain my point, can be any).
- Just a thought, can be potentially good interview question also.
Virtualization blog 