As with most debates, the truth lies somewhere in the middle. Many (if not most) of the benchmarks in our suite measure the alacrity of x86 computing resources in a very real-world way. Others focus more intently on graphics performance. And were increasingly adding tests able to leverage what AMD calls heterogeneous computingimproving performance by drawing from multiple subsystems concurrently.
The point is that x86 cores are still first-class citizens in the APU world, and there is such a thing as performance thats not good enough. Thats part of the reason why so many of us want to know how the Piledriver architecture improves upon Bulldozer. So lets get that out of the way first.
We took the A10-5800K, set it to 3.8 GHz, turned off Turbo Core and any power-saving feature thatd spin the chip down. Then, we took FX-8150, overclocked it to 3.8 GHz, and disabled all of the same features. By running a single-threaded workload like iTunes, we could neutralize the difference in core count (though, if anything, FX could have benefited from its 8 MB L3). Nevertheless, Piledriver clearly completes our workload much faster, yielding a 15% improvement, per clock cycle, over Bulldozer.
Turning off two of FX-8150's Bulldozer modules gives us the opportunity to run a threaded workload like 3ds Max without slanting the result toward Bulldozer. And once again, the Piledriver-based APU wins by roughly 15%.