Originally Posted by dave12
My understanding was that the core could accept two incoming instructions per cycle giving each about 65 percent of what it would if it was only accepting one. Giving a 30ish percent increase over single thread performance, but the single threaded stuff that doesn't like HT had me a smidge uncertain.
HT allows the CPU to prepare 2 tasks at the same time, and execute them in simultaneus-like manner, while still calculating only 1 task's data at a time.
The performance of the core is identical as the performance of non-HT CPUs, but the bottleneck of the front-end is removed, thus giving you the feeling of 30% boost
CPU can't give 65% to two tasks, cause it doesn't have more than 100% resources.
The thing with FPS comes from the fact that single- or multi-threaded games do not benefit from duplicated architecural states, but from duplicated cores (dual core or more), But HT stucks 2 threads on the same core, instead of spreading them across cores (because the OS doesn't really know 1&2 core together perform slower than 1&3 core).