http://ixbtlabs.com/articles3/...chspeed-2009-4-p1.html
However, we expected better results. Having seen a 10.2% performance gain with a quad-core processor, we actually expected at least 20% with a single core. Alas, it did not happen. When you already know test results, it makes no sense to speculate whether it's good or bad -- facts are neutral. We feel sorry for the dream: if HT efficiency had raised significantly when the number of cores is decreased, we might have hoped to see dual-core CPUs with HT support from Intel in the nearest future to be positioned as an alternative to cheap honest quad-core processors from AMD. Considering generally higher performance of the new core from Intel per MHz -- why not?
However, 10-11% advantage, provided by HT, won't be enough for the virtual quad-core processor to compete with a real one. So from the point of view of providing a real performance advantage, Intel has no objective incentive to promote Hyper-Threading to Low-End. HT does not provide a sufficient performance gain to help expensive (relative to dual-core processors from AMD) dual-core processors from Intel to stand up to cheap (relative to quad-core processors from Intel) quad-core processors from AMD. However, pointlessness from the practical point of view does not at all mean that omnipresent marketing specialists won't try to use this resource.
However, there is another conclusion suggested by results of these tests. Indeed, 11 "red cards" for performance drops in HT tests with four physical cores have magically turned into two cards in our tests with a single core. But this technology hasn't changed: because we use the same processor. So our conclusion is quite optimistic: perhaps the problem is not in the hardware optimization of Hyper-Threading. It's reasonable to assume that Windows Vista was so stupefied to detect eight processors that its task scheduler just couldn't cope with such an abyss of new opportunities. At least this explanation to so many HT failures with an 8-processor system (from the OS point of view) seems the most logical to us. So if we take this as a working hypothesis, the problem is in system software only, and the situation can be improved without changing the hardware (that is it's not Intel's fault).