CPU test of headline has some bugs to work out. HTT is mucking with the CPU results, like I thought it was.
Look at it logically: If I have 4 cores, and I do the same amount of work in 4 threads, you would expect linear absolute performance gains up to 4 threads, correct?
Taking a look at two 2600(k) runs:
http://www.headline-benchmark.com/results/c309c1f4-6f00-4def-8127-b8d679fe5989
http://www.headline-benchmark.com/results/93a871e9-4a76-42aa-8f91-ef08fedef7dc
Notice the various dropoffs in performance as threads increase? That shouldn't be happening, unless multiple threads are getting stuck on the same core, OR a HTT core is getting used before a "full" core, and the shared frontend is causing massive performance drops.
Compare that to this run:
http://www.headline-benchmark.com/results/359025ad-a71c-4df1-a21e-2dcac265a956/87080cac-179d-4a2c-a2a9-cb1e90667a3f
Where I disabled the HTT cores, and compared against my last benchmarks. Note how the performance dropoffs vanished, and in some cases, performance improved by DISABLING cores?
Now, we still have an issue where performance stalls. What I *think* is going on, is multiple threads are going to the same core, so performance flatlines, then jumps by double the next time a thread gets assigned, maxing at about 5 threads (remember: HTT cores disabled). So in the case of the Integer test, I think the treads are being assigned like this:
Thread 1: Core 0
Thread 2: Core 1
Thread 3: Core 0/1
Thread 4: Core 2
Thread 5: Core 3
Hence why performance stalls on three threads, then increases linearly up to 5 (which doesn't make sense for a quad). Same thing likely happening in the FP test:
Thread 1: Core 0
Thread 2: Core 0
Thread 3: Core 1
Thread 4: Core 1
Thread 5: Core 2
Based on the huge jump going from 4 to 5, I'd suspect one of the other threads gets reassigned to core 3 at some point, but I'd need to break out my low level debug tools to prove this.
Ags1, I'd recommend that you manually assign threads to cores for this test. Start with the Even (Non HTT/CMT) cores, then proceed to the Odd ones. Once you have more threads then cores, don't bother anymore (really doesn't matter at that point). That should remove the Windows scheduler from affecting performance...Right now, due to HTT having a much higher performance cost if used wrong, Intel's numbers are probably grossly understated in your benchmark. [Can't wait to see the response to THAT one.]