F5F Stay Refreshed Hardware Desktop Area for HT/SMT components, future perspectives extended

Area for HT/SMT components, future perspectives extended

Area for HT/SMT components, future perspectives extended

Pages (2): 1 2 Next
S
Skylaire
Member
104
10-25-2025, 07:07 PM
#1
Considering the recent security issues, I began questioning whether HT or SMT would no longer be relevant. While SMT isn't directly affected, I'm assessing the industry's possible direction. The key points are: implementing HT/SMT incurs costs like increased die size and power consumption. Do the performance benefits justify these expenses? If cores become abundant, do we still require extra threads? Absent HT/SMT, critical path threads sharing cores with less vital code would be less likely to slow things down. Consistent performance seems more valuable than peak speed, though peak performance may still exist in certain processors. I'm observing a trend toward more cores, especially with AMD leading the way. Some applications scale well, while others struggle due to architectural constraints. The challenge lies in determining whether the added complexity of HT/SMT remains necessary or if it's becoming obsolete. References from the P4 era suggest a 5% die area increase, which is modest compared to gains. However, since CPU designs have evolved significantly, it's unclear if that figure holds today. The complexity of new features might require even more intricate HT/SMT solutions, making the trade-off harder to evaluate. I'm seeking clearer data on actual die area usage and performance metrics to make a more informed judgment.
S
Skylaire
10-25-2025, 07:07 PM #1

Considering the recent security issues, I began questioning whether HT or SMT would no longer be relevant. While SMT isn't directly affected, I'm assessing the industry's possible direction. The key points are: implementing HT/SMT incurs costs like increased die size and power consumption. Do the performance benefits justify these expenses? If cores become abundant, do we still require extra threads? Absent HT/SMT, critical path threads sharing cores with less vital code would be less likely to slow things down. Consistent performance seems more valuable than peak speed, though peak performance may still exist in certain processors. I'm observing a trend toward more cores, especially with AMD leading the way. Some applications scale well, while others struggle due to architectural constraints. The challenge lies in determining whether the added complexity of HT/SMT remains necessary or if it's becoming obsolete. References from the P4 era suggest a 5% die area increase, which is modest compared to gains. However, since CPU designs have evolved significantly, it's unclear if that figure holds today. The complexity of new features might require even more intricate HT/SMT solutions, making the trade-off harder to evaluate. I'm seeking clearer data on actual die area usage and performance metrics to make a more informed judgment.

T
Tvender
Junior Member
12
10-26-2025, 08:22 PM
#2
HT/SMT uses minimal physical die space because it operates virtually, relying on simulation and design tools rather than requiring large hardware footprints.
T
Tvender
10-26-2025, 08:22 PM #2

HT/SMT uses minimal physical die space because it operates virtually, relying on simulation and design tools rather than requiring large hardware footprints.

L
LLalande
Junior Member
10
10-27-2025, 06:12 PM
#3
1. The abbreviation in this case refers to something specific, but its exact meaning isn't clear here.
2. Perhaps I'm not sure about this.
L
LLalande
10-27-2025, 06:12 PM #3

1. The abbreviation in this case refers to something specific, but its exact meaning isn't clear here.
2. Perhaps I'm not sure about this.

A
Angel_Wingsx_
Member
160
10-27-2025, 07:45 PM
#4
requires adjustments to the FPU and pipeline prior to and following the CPU. edit: this must be integrated into the design and architecture.
A
Angel_Wingsx_
10-27-2025, 07:45 PM #4

requires adjustments to the FPU and pipeline prior to and following the CPU. edit: this must be integrated into the design and architecture.

M
Misdoing
Junior Member
17
10-29-2025, 05:20 PM
#5
AMDs implementation of Hyper Threading is called Simultaneous Multi Threading.
M
Misdoing
10-29-2025, 05:20 PM #5

AMDs implementation of Hyper Threading is called Simultaneous Multi Threading.

T
tamemarco
Senior Member
482
10-30-2025, 02:08 PM
#6
It isn't free; you need to build it in silicon if you want it. Certain sections must be repeated to ensure that additional thread. Parallel multi-threading is possible. You can interpret this as AMD's version of HT, or the general term for what HT represents.
T
tamemarco
10-30-2025, 02:08 PM #6

It isn't free; you need to build it in silicon if you want it. Certain sections must be repeated to ensure that additional thread. Parallel multi-threading is possible. You can interpret this as AMD's version of HT, or the general term for what HT represents.

F
Fernan_Gamer
Junior Member
40
10-31-2025, 11:58 PM
#7
It seems the idea was simply embedded in the CPU's instructions, not a physical component.
F
Fernan_Gamer
10-31-2025, 11:58 PM #7

It seems the idea was simply embedded in the CPU's instructions, not a physical component.

A
aadnemellum
Junior Member
49
11-01-2025, 12:34 AM
#8
Dammit, was hoping to fix a typo before anyone quoted it
A
aadnemellum
11-01-2025, 12:34 AM #8

Dammit, was hoping to fix a typo before anyone quoted it

C
cj3406
Junior Member
7
11-01-2025, 06:44 AM
#9
Sure, I see the mistake now—it wasn't Silicon. I've corrected my quote for you.
C
cj3406
11-01-2025, 06:44 AM #9

Sure, I see the mistake now—it wasn't Silicon. I've corrected my quote for you.

P
pvpking1234
Member
70
11-02-2025, 04:25 PM
#10
P
pvpking1234
11-02-2025, 04:25 PM #10

Pages (2): 1 2 Next