• 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.

Criteria for determining CPU issue width

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
There are always many more threads running than you know. SMT helps with this. It may not be the best solution, but these days it almost always works out for the better.
 
It was just a example. With SMT you got more slower threads with increased thread count, which combined netted more throughput than without SMT. The point was, the more thread per core the slower those individual threads will be and it's not ideal solution for every case, most workloads prefer faster individual threads - SMT for desktop and mobile oriented workloads just isn't good solution.
I disagree. MOST CPU's, Intel and AMD (Ryzen specifically) in MOST applications will benefit greatly from using SMT on desktop and mobile. There are only a few cases where SMT is a hindrance.
 
It was just a example. With SMT you got more slower threads with increased thread count, which combined netted more throughput than without SMT. The point was, the more thread per core the slower those individual threads will be and it's not ideal solution for every case, most workloads prefer faster individual threads - SMT for desktop and mobile oriented workloads just isn't good solution.
Any operating system with proper thread priority could solve this. Current cores are only 7-8 wide because any additional units would be wasted most of the time. With higher SMT, those units can be effective even for realistic code and be available for use by really well-written code.
 
Back
Top