The launch of Bulldozer in October wasn't exactly a success for AMD. In our review, Anand ended up recommending the Intel i5-2500K over AMD FX-8150. One of the reasons behind the poor performance of Bulldozer is its unique design: each Bulldozer module consists of two integer and one floating point core. Todays operating systems don't know how to optimally schedule threads for this design and as a result, the full potential of Bulldozer has not been achieved. Microsoft has released a hotfix for Windows 7 and Server 2008 R2 that should increase the performance of Bulldozer.

Let's look at the problem to see what happened and how the hotfix helps address it. Before the update, Windows didn't know how to ideally schedule threads on Bulldozer. Essentially, it didn't know when it was good to place threads on single module versus multiple modules.

The picture above explains this pretty well. Before the update, Windows more or less randomly placed the threads which meant many modules were unnecessarily active at the same time. This capped the maximum Turbo speeds because those can only be achieved when some of the modules are inactive (power gated).

VR-Zone is claiming that Windows sees one Bulldozer module as a single multi-threaded core, similar to an Intel Hyper-Threading core. Basically, your 8-core FX-8150 is seen as a quad-core, 8-thread CPU—just like Intel's i7-2600K for instance. This goes against AMD's design and marketing because Bulldozer is closer to an 8-core CPU.

We have not yet tested Bulldozer with the hotfix, but don't expect miracles as Microsoft is suggesting a 2-7% increase. Better scheduling for the Bulldozer CPUs will improve performance a bit, but not enough to close the gap in many scenarios. Windows 8 already has the new thread scheduler, and according to AMD's own and third party tests the performance increase is up to around 10%, but Bulldozer needs a lot more than 10% to surpass Sandy Bridge.

Update: VR-Zone reports (and we can confirm) that the download link for the hotfix is no longer functional. There were apparently unexpected performance drops in some cases after applying the hotfix and Microsoft is investigating the issues. Modifying the scheduler in Windows is not something to be done lightly, as it changes a core element of the OS, so more testing and validation for such updates is always a good idea.

Update 2: Apparently there is a second part to the hotfix that was not pushed live, and this hotfix was pushed live prematurely.