[citation][nom]amk-aka-phantom[/nom]You've got to be kidding! Wait ANOTHER year? What, 3 years was not enough?So, now AMD fanboys are finding all kinds of excuses for Bulldozer underperforming... Intel compiler conspiracy, huh? Well, BD was supposed to be a gaming beast, and i5-2500K beat it in all games, ESPECIALLY CPU-heavy (WoW). Say what you will, but Bulldozer failed miserably for its intended audience, I hope it will be worth it for a worstation; I'll wait for some more benchmarks - maybe it'll be good for something else than gaming... can't imagine what, though, since it lost to 2500/2600K in nearly all tests.Before you whine about how all these programs are Intel-biased, let me remind you that Mr. Angelini here tested Bulldozer in many, many popular applications and benchmarks... he was probably shocked and was desperately trying to find at least SOMETHING where BD would excel, but failed. I don't blame him, hell no, great review - I'd be shocked, too! I imagine how he was going through the benchmarks, each time the same thing... Core i5/i7 on top... and Phenom X6 beating BD must've caused him to either crack with laughter or triple-check all components. Mr. Angelini, am I right? TL;DR: you might say that the benchmarks and games used here are Intel-biased, but that was the most popular and widespread software. If AMD can't make their CPU work with them...Next AMD fan excuse prediction: Tom's got a faulty chip for testing, aka Bulldozer w/o a shovel.Oh, and before you flame me and call me an AMD hater, I love their graphics cards... somehow AMD is great on that market, no matter how evil Intel and nVidia conspire against them Why is that?[/citation]
You're correct in that I double- and triple-checked the results. I even sent my entire list of results to AMD a week prior to the review going live to let them look at the performance I was seeing. None of what I turned up was unexpected.
I still maintain that something is wrong with F1 2011 on the AMD platform. But I've been telling AMD for more than a year now (since F1 2010) that there's something going on there. At this point, shoot, maybe it's just *that* processor-bound?