Don’t forget to set the advanced ESXi setting “Cpu.PcpuMigrateIdlePcpus” back to its default value of 4 if it was changed to 0 as a workaround for the issue described in http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033780.

In over-committed CPU environments (VDI), having Cpu.PcpuMigrateIdlePcpus disabled can increase CPU Ready time. It should be set back to its default of 4 as the official patch for the issue (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2051208) states.

Here is a 6-month graph for a single host (CPU | Ready) showing the 5-month period where Cpu.PcpuMigrateIdlePcpus was disabled in mid-February and re-enabled (back to default) a few days ago:

The setting can be changed quickly and easily across all hosts via PowerCLI: Set advanced settings on all hosts.