• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Drawbacks from Hyper-Threading

Are there any major consumer relevant drawbacks / cons in the implementation of hyper-threading? Essentially, what has to be sacrificed in the doubling of a chips total threads? Similarly, hyper-threading and competing virtual core solutions seems to be a no brainer to amplify a chips performance in certain scenarios without increasing the die size, so why is this not yet a commodity in the chip market?

I know there are probably major flaws in the logic behind my assumptions, but I have failed to find a suitable answer to this question that has been knawing at my brain regarding the entire industry!
 
There isn't any downsides for end users. You may see a tiny downside if you run something like Linpack. But that's pretty much the only thing I can think on.
 
Power consumption is the most probable, perhaps due to the additional hardware to enable it. It used to be that Hyperthreading incurred a minor single-thread performance hit, but between wider cores and modern OSs built to handle the threads, this is no longer an issue.
 
Power consumption is the most probable, perhaps due to the additional hardware to enable it. It used to be that Hyperthreading incurred a minor single-thread performance hit, but between wider cores and modern OSs built to handle the threads, this is no longer an issue.

Then is it possible that we will see the widespread use of virtual cores in mobile, such as multiple virtual cores being used with fewer physical cores in a big.LITTLE setup? Or are the differences between mobile and desktop workloads too great for such an analogy to be plausible / worthwhile? Also, is there a future scenario in which Intel drops half the cores in their lower end processors to free up die, but adds HT, and then proceeds to increase the size of their integrated graphics?

Also, thanks for the replies. I've been really caught up on this subject lately and you have been of great help.
 
Last edited:
Power consumption is the most probable, perhaps due to the additional hardware to enable it. It used to be that Hyperthreading incurred a minor single-thread performance hit, but between wider cores and modern OSs built to handle the threads, this is no longer an issue.

It used to be that one could see resource-starvation inside the cores for certain threads, if their "pair" thread was a heavy resource user.

This changed, I believe in IVB, where HT could more fairly allocate the internal chip resources, and in HSW, they added the feature that if one thread was running without a "pair" thread, then it could allocate more of those core resources, but then they would be freed up if another thread got scheduled with that thread.

And overall resource counts internal to the core got increased in SKL, so it's even less of a problem.
 
As far as I am aware, HT (SMT) is orthagonal to the issues surrounding BIG.little. One can have one with or without the other.
Exclusive big core designs like Apple's A9 would be the primary benefactors from SMT. Kyro would also probably have been a pretty good candidate as they focus on power gating on a per-core basis and per-core performance tends to be pretty high (if due to high clocks).

Not sure how SMT would benefit mobile though. Multitasking is rarely demanding on these platforms that they'd choke a pair of competent cores, let alone a quad.
 
Last edited:
On this subject, am I right in saying that all Skylake/Haswell etc cores have the HT hardware built into them, only it's disabled on the i5s/Celerons/Pentiums? So it's not like the core was designed and then HT added on the i3s and i7s, rather the core was very much designed with HT in mind but in such a way the circuits could be disabled where needed for certain models. So there'd be nothing theoretically stopping Intel from making all subsequent Skylake CPUs have HT enabled (although that would seriously mess up the segmentation of the i3>i5>i7 I know....I'm basically wondering if there's a technical reason for i5s not having HT rather than a marketing/business one).
 
Last edited:
On this subject, am I right in saying that all Skylake/Haswell etc cores have the HT hardware built into them, only it's disabled on the i5s/Celerons/Pentiums? So it's not like the core was designed and then HT added on the i3s and i7s, rather the core was very much designed with HT in mind but in such a way the circuits could be disabled where needed for certain models. So there'd be nothing theoretically stopping Intel from making all subsequent Skylake CPUs have HT enabled (although that would seriously mess up the segmentation of the i3>i5>i7 I know....I'm basically wondering if there's a technical reason for i5s not having HT rather than a marketing/business one).
All Skylake cores (well, any big core since the first i7) has HT circuitry in hardware regardless of sku. The decision to disable it or not is solely a business decision.
 
On this subject, am I right in saying that all Skylake/Haswell etc cores have the HT hardware built into them, only it's disabled on the i5s/Celerons/Pentiums? So it's not like the core was designed and then HT added on the i3s and i7s, rather the core was very much designed with HT in mind but in such a way the circuits could be disabled where needed for certain models. So there'd be nothing theoretically stopping Intel from making all subsequent Skylake CPUs have HT enabled (although that would seriously mess up the segmentation of the i3>i5>i7 I know....I'm basically wondering if there's a technical reason for i5s not having HT rather than a marketing/business one).

HT have been segmented since the P4. Core 2 actually had HT but disabled for all parts. All Skylake parts also got an EDRAM controller.
 
Is there a limitation on how many virtual cores one can have for every physical one? For example, for shits and giggles could Brian Krzanich decide he wants to upgrade his sick gaming build with a single core, 8 thread processor (the i9 1337K with quad HT) knowing full well he will not have equal performance to a true octo-core processor?
 
Is there a limitation on how many virtual cores one can have for every physical one? For example, for shits and giggles could Brian Krzanich decide he wants to upgrade his sick gaming build with a single core, 8 thread processor (the i9 1337K with quad HT) knowing full well he will not have equal performance to a true octo-core processor?

You can more or less have as many as you like. Xeon Phi got 4 per core. Sparc and Power have done 8 per core.

You just need a wide enough core with a lot of regularly wasted execution units for it to work. (This is also why Linpack doesn't scale with HT).
 
Hyperthreading produces a bit more heat when the extra threads are being used and it may take a bit more voltage for a CPU with HT to be stable at a given frequency. That's from the increased work the cores are doing and the extra stress that increase causes, respectively.
 
So there'd be nothing theoretically stopping Intel from making all subsequent Skylake CPUs have HT enabled (although that would seriously mess up the segmentation of the i3>i5>i7 I know....I'm basically wondering if there's a technical reason for i5s not having HT rather than a marketing/business one).

It's possible that models without HT are binned with models that the HT portion is busted but that would be pretty low number I think. It's more likely fused off for marketing purposes.
 
It's possible that models without HT are binned with models that the HT portion is busted but that would be pretty low number I think. It's more likely fused off for marketing purposes.

If HT is busted so is the core. HT is only disabled due to segmentation.

Example from P4.
die.jpg
 
Source please? I've been on these forums for a long time, and I have never heard that. Did Pentium-M have HT? I didn't think so on that core either.

I also never heard of this before, it also wouldn't make sense for them to never enable even for some Xeon models, unless HT was not there or broken.

I mean Willamette P4 had HT but was never used, but some Xeon parts based on the same core had it enabled.

as others have mentioned HT will probably increase power usage, and while rare these days it still can reduce performance in some conditions
 
If HT is busted so is the core. HT is only disabled due to segmentation.

In Skylake Intel duplicated some of the back-end resources and gave each of the two threads a dedicated one. It would now be theoretically possible for there to be a defect that killed the second thread while not hurting the first.

I don't know if Intel uses this to bin any chips, though.
 
Back
Top