I know this is old news, but at a recent meeting at vmware 4 different customers agreed that they were taught something different by instructors in Denmark about Co-scheduling.

The myth that all 4 of us believed in states that:

“An 8 vCpu machine can only get cpu time, if 8 cores are available to the scheduler”, so if 7 cores were available the machine would wait, which you could see from the cpu-ready counters.

However since ESX 3.X vmware has done something called “relaxed co-scheduling”, meaning that if a machine has 8 vCpu’s but only has a single threaded application it can run if fewer than 8 cores were available to scheduler.

See Duncans post about this from 2008!

We’ve done a load test of a SharePoint 2013 farm which consisted of 2 front-end servers each with 24 vCpu’s that were run on a 4-way server with 8 cores in each processor, on vSphere 5.0.

loadtest showing cpu ready

Had strict co-scheduling still existed we should have seen CPUREADY %’s above 50% instead we got a peak at 33%. That however shows that we’re still over comitting the host too much.

First post.

Why another blog you might ask.

Well I don’t have any ideas about becoming a top 25 blogger, gunning for fame and all that. But I do however occasionally come across stuff that i think others might find interesting, and figured that I might as well write it down somewhere. So why not use a free blogging service for that.

So welcome to my blog. I hope to have some content over time, but I wont promise stuff weekly or even monthly 🙂



Essense of virtualization


A Virtualization Blog

Go Software Defined

vSphere - The foundation of every Datacenter.


The weblog of an IT pro specializing in virtualization, storage, and servers

Virtual Geek

A Virtualization Blog

Perfect Cloud

Virtualize everything!

Yellow Bricks

by Duncan Epping

%d bloggers like this: