Ags1 :
Jed, I find those bit-tech results a bit hard to believe. It's all very well to say they did a 'real-world' bench using Gimp, but which parts of Gimp? Seeing how the i3 places relative to the i5 I would say the test is single threaded. They also mention the test results rely on memory and storage performance, which means they are not doing a pure test of the CPU. Which is why I prefer synthetic benchmarks, and of course wrote one myself.
The handbrake result also looked a bit off to me, and I recall Tom's also used handbrake in their FX8350 review, and got totally different results:
http://www.tomshardware.com/reviews/fx-8350-vishera-review,3328-12.html
To be fair, real world tasks are hardly ever going to be synthetic.
Also, next time I run the benchmark, I'm going to pay a LOT more attention to the CPU test on where threads are getting assigned. Looking at the 2600k versus 8350 results, I would *expect* the 2600k to win up to 4 threads, start falling behind in 5-8 threads, then pull ahead again above 8 threads. I don't see that.
http://www.headline-benchmark.com/results/c309c1f4-6f00-4def-8127-b8d679fe5989/9a411141-526d-4452-8e78-1c9891c2efa0
Kinda makes me wonder if the HTT cores are getting loaded before the full cores...In any case, for both CPU's, I'd expect close to linear performance gains up to 4 cores [no *major* internal CPU bottlenecks], then lesser gains due to the performance hits of HTT/CMT (with larger gains for AMD from this point forward, eventually passing Intel in performance). Basically, I'm going to check to make sure the cores are loaded on my 2600k in this order: 0,2,4,6,1,3,5,7, loading the HTT cores last during the threading CPU test.
Another thing I might do is force the application affinity to just one core, to see how the 2600k does on each test when threads are fighting over CPU resources. Might be a good *core for core* test to throw in: See how a single core does when 8+ threads are trying to use it.