Conclusions: SMT On

I wasn’t too sure what we were going to see when I started this testing. I know the theory behind implementing SMT, and what it means for the instruction streams having access to core resources, and how cores that have SMT in mind from the start are built differently to cores that are just one thread per core. But theory only gets you so far. Aside from all the forum messages over the years talking about performance gains/losses when a product has SMT enabled, and the few demonstrations of server processors running focused workloads with SMT disabled, it is actually worth testing on real workloads to find if there is a difference at all.

Results Overview

In our testing, we covered three areas: Single Thread, Multi-Thread, and Gaming Performance.

In single threaded workloads, where each thread has access to all of the resources in a single core, we saw no change in performance when SMT is enabled – all of our workloads were within 1% either side.

In multi-threaded workloads, we saw an average uplift in performance of +22% when SMT was enabled. Most of our tests scored a +5% to a +35% gain in performance. A couple of workloads scored worse, mostly due to resource contention having so many threads in play – the limit here is memory bandwidth per thread. One workload scored +60%, a computational workload with little-to-no memory requirements; this workload scored even better in AVX2 mode, showing that there is still some bottleneck that gets alleviated with fewer instructions.

On gaming, overall there was no difference between SMT On and SMT Off, however some games may show differences in CPU limited scenarios. Deus Ex was down almost 10% when CPU limited, however Borderlands 3 was up almost 10%. As we moved to a more GPU limited scenario, those discrepancies were neutralized, with a few games still gaining single-digit percentage points improvement with SMT enabled.

For power and performance, we tested two examples where performance at two threads per core was either saw no improvement (Agisoft), or significant improvement (3DPMavx). In both cases, SMT Off mode (1 thread/core) ran at higher temperatures and higher frequencies. For the benchmark per performance was about equal, the power consumed was a couple of percentage points lower when running one thread per core. For the benchmark were running two threads per core has a big performance increase, the power in that mode was also lower, and there was a significant +91% performance per watt improvement by enabling SMT.

What Does This Mean?

I mentioned at the beginning of the article that SMT performance gains can be seen from two different viewpoints.

The first is that if SMT enables more performance, then it’s an easy switch to use, and some users consider that if you can get perfect scaling, then if SMT is an effective design.

The second is that if SMT enables too much performance, then it’s indicative of a bad core design. If you can get perfect scaling with SMT2, then perhaps something is wrong about the design of the core and the bottleneck is quite bad.

Having poor SMT scaling doesn’t always mean that the SMT is badly implemented – it can also imply that the core design is very good. If an effective SMT design can be interpreted as a poor core design, then it’s quite easy to see that vendors can’t have it both ways. Every core design has deficiencies (that much is true), and both Intel and AMD will tell its users that SMT enables the system to pick up extra bits of performance where workloads can take advantage of it, and for real-world use cases, there are very few downsides.

We’ve known for many years that having two threads per core is not the same as having two cores – in a worst case scenario, there is some performance regression as more threads try and fight for cache space, but those use cases seem to be highly specialized for HPC and Supercomputer-like tasks. SMT in the real world fills in the gaps where gaps are available, and this occurs mostly in heavily multi-threaded applications with no cache contention. In the best case, SMT offers a sizeable performance per watt increase. But on average, there are small (+22% on MT) gains to be had, and gaming performance isn’t disturbed, so it is worth keeping enabled on Zen 3.

 
Power Consumption, Temperature
Comments Locked

126 Comments

View All Comments

  • dotjaz - Thursday, December 3, 2020 - link

    Do you understand what "S(imultaneous)" in SMT means? Barrel processors are by definition NOT simultaneous. They switch between threads.
  • quadibloc - Friday, December 4, 2020 - link

    That all depends. There could be a unit that switches between threads to dispatch instructions into the pipeline, but instructions from all the threads are simultaneously working on calculations in the pipeline. I'd call that a way to implement SMT.
  • Elstar - Friday, December 4, 2020 - link

    Guys, I've got bad news for you. The difference between a barrel processor ("temporal multithreading") and SMT is all about the backend, not the frontend. I.e. whether the processor is superscalar or not. Otherwise there is no difference. They duplicate hardware resources and switch between them. And the frontend (a.k.a. the decoder) switches temporally between hardware threads. There are NOT multiple frontends/decoders simultaneously feeding one backend pipeline.
  • Elstar - Friday, December 4, 2020 - link

    For example the "SMT4" Intel Xeon Phi has a design weakness where three running threads per core get decoded as if four threads were running. (And yes, just one or two running threads per core get decoded efficiently.)
  • dotjaz - Thursday, December 3, 2020 - link

    You nailed 2 letters out of 3, gj.
  • Luminar - Thursday, December 3, 2020 - link

    Talk about being uninformed.
  • MenhirMike - Thursday, December 3, 2020 - link

    Will be interesting to see if this looks different with Quad-Channel Threadripper or Octo-Channel EPYC/TR Pro CPUs, since 16 Cores/32 Threads with 2 channels of memory doesn't seem very compute-friendly. Though it's good to see that "SMT On" is still the reasonable default it's pretty much always has been, except in very specific circumstances.
  • schujj07 - Thursday, December 3, 2020 - link

    Also would be interesting to see this on a 6c/12t or 8c/16t CPU.
  • CityBlue - Thursday, December 3, 2020 - link

    In your list of "Systems that do not use SMT" you forgot:

    * All x86 from Intel with CPU design vulnerabilities used in security conscious environments
  • MenhirMike - Thursday, December 3, 2020 - link

    To be fair, "x86" and "security conscious" are already incompatible on anything newer than a Pentium 1/MMX. Spectre affects everything starting with the Pentium Pro, and newer processors have blackboxes in the form of Intel ME or AMD PSP. You can reduce the security risk by turning off some performance features (and get CPUs without Intel ME if you're the US government), but this is still just making an inherently insecure product slightly less insecure.

Log in

Don't have an account? Sign up now