vSphere DRS - CPU overcommit and it's relationship to ESX host memory

Hi all,

I think I've got this straight in my head, but wanted to run it past the community.

I have a cluster with 8 hosts in it.

2 of these hosts are reporting critically high memory usage, but DRS is failing to rebalance the cluster.

The remainder of the nodes in the cluster are reporting low / normal levels of memory use.

I've observed that CPU overcommit has been disabled for the cluster.

\--

So if I understand correctly, by disabling CPU overcommit, DRS is forced to place VMs onto hosts where they have 1:1 usage of physical CPUs. Could this configuration result in DRS being **unable** to re-balance machines correctly, even though there's available memory on the other nodes.

To correct this memory contention issue, if we re-enable a modest level of CPU overcommit, we'll allow DRS to properly rebalance the cluster, resolving the memory contention.

Is my understanding correct?

​

​