May 07, 2021

We used the VMCO fling to optimize our VMs and made many changes over the past month. A lot of our VMs are 4+ cores, many 8 and 16 cores, and it suggested we move all our VMs to 1 socket and (4, 8, and 16) core setups.

However, our CPU ready time was astronomical... Like 80,000+ ms. Our CPU utilization on each host was only ~25%. We are running single-socket EPYCs host, each with 64 cores/128 threads.

We have since moved almost all of our VMs back to (1) core-per-socket and 4, 8, and 16 sockets. Now our CPU ready time is ~100ms or less for most of our VMs, 300-400ms for some of the heavy hitters.

Since moving back to (1) core-per-socket the VMs feel snappier but we made the changes yesterday and haven't had time to do proper testing. Any suggestions?

May 07, 2021

Hi Mark,

Where is this recommendation coming from? "The Host Power Policy is recommended to be set to High Performance
for VMs with more than 8 vCPUs"?

Apr 14, 2021

Hi Mark,

Many VMs reported as VMs Optimized "NO". Do we need to consider OptimalSockets and OptimalCoresPerSocket value to fix?

Apr 15, 2021

Hi Karthikeyan,
Yes, when the VM reports NO for Optimized, you can follow the recommendation to reconfigure it so it will be optimized. The recommendation is to start with the "high" priorities and work your way down to the lows. Fixing all the lows is usually daunting, so the best way to attack that is to correct templates and future VMs that are created.

Oct 12, 2020

HI Mark,

Appreciate everything that you are doing here.. Trying to run VMware Compute Optimizer (VMCO). But couldn't be able to find the Get-"OptimalvCPU_v2.1.0.ps1" file anywhere.. Could you please help us here..

Oct 19, 2020

Hi Ck, sorry for the slow reply, as I was on vacation last week! Make sure you have both .ps1 files in the same directory when you launch the "Virtual_Machine_Compute_Optimzer_v2.1.0.ps1" script. It will look for it in the same directory.