[quotemsg=9533687,21,134065]Don't worry--I'm working on the data right now. As it stood, this story took more than a week of all day/all night testing, troubleshooting, new BIOS installing, and re-testing to nail down. It can go on indefinitely if you let it ;-)[/quotemsg]
First of, I'd like to say I'm a fan of your work, how you get so in-depth with details and the workings of stuff, in other words, how you explain stuff thoroughly. :-D Anyway, I wish manufacturers would give you more samples of the same hardware so you could work in parallel and be able to get more benchmarks through quicker and more easily. But I do hope if ever that that's the case with the slight delay and not a lack of manpower or something, that is if you don't prefer just working alone. Keep up the good work and I'll be most surely looking forward to more info you could generate about Trinity in the future, and maybe more so for a Vishera (I hope I got that right for the vanilla Piledriver). Good luck!
That aside... In addition to what I said above about the floating-pointing units performing a lot better, since I did notice that Trinity is running on a higher clock-rate, does that mean that the integer cores haven't improved that much if they perform somewhat on par with Llano's? I don't mean to add more work for you (guys), but maybe a benchmark of integer- and floating-point intensive applications along with multi-, lightly-, and single-threaded applications is in order? Or is the rough 15% improvement over Bulldozer enough to calculate how Trinity performs compared to Llano (their Pildriver and Husky/Stars cores more specifically)? I might've sounded like newb in anything I said above so pardon that if ever.
(If ever you read this blazorthon, thanks for pointing out/clarifying to me what Vishera and Husky are.)