Threadripper 2: Filling Out The Product Portfolio

With the quad silicon die strategy for Threadripper 2, there are plenty of ways that AMD could have chopped and changed the core counts to get various processors at various price points. For Intel, having a product at every pair of core counts seems to be integral to the company strategy, producing seven different processors from six cores to eighteen cores, whereas AMD has decided to split into 12, 16, 24, and 32.

We reviewed the 32-core Threadripper 2990WX and the 16-core Threadripper 2950X back in August. The results from that review were very mixed: the large 32-core behemoth was an absolute beast in non-communication limited workloads (either to memory or other cores), and absolutely broke down anything the competition had to offer. On the catch side, that didn’t apply to everything, and in the communication limited cases, the 2950X was preferred, especially as it was a lot cheaper. Expanding out to the quad-die strategy, as AMD has done, with two of those dies not being directly connected to memory, both helps and hinders performance. The upshot is that for the price of Intel’s 18-core, users could get 32-cores from AMD, if you can use them. In that review, out of the Threadripper family, we said that the 2950X was likely where users looking for the best performance per dollar were likely to end up.

Today sees the launch of the other two processors in the family, the 12-core 2920X and the 24-core 2970WX. There is ultimately less fanfare with these parts, being cut down versions of the previous two, and so on paper, given the same or lower frequencies, we would normally expect them to perform worse than the 2990WX and 2950X. This would be a good reason as to why they’ve been released a little bit later. In our performance testing, this kind of bears fruit, but not always.

In our power analysis, having fewer cores per die means that we see a sharper uptick in power consumption when threads are placed onto a new die. This is because the new die is ‘cool’, in the sense that nothing is running on it, and as a result the cut down dies actually hit their peak power sooner, which should translate into frequency. However, it really does depend on the workload, and most user workloads either use all of the cores, or just a few. In order to get the benefit here, we’re looking at multi-taskers.

For performance, in most multithreaded benchmarks we see the 2920X sitting below the 2950X, and the 2970WX sitting below the 2990WX. This is mostly because of core counts, but depending on how the benchmark scales and memory accesses, we do see the 2970WX sometimes go above the EPYC 7601 with its lower frequency, despite its higher memory bandwidth. At $1299, the 2970WX is going to be $500 cheaper than the 2990WX, which certainly makes it aggressive for price/performance.

Blender 2.79b bmw27_cpu Benchmark

We do see on occasion that the 2970WX actually beats the 2990WX, such as in PhotoScan, 3DMark Physics and GeekBench, because there are fewer cores to compete for the inter-core bandwidth. However on the whole, the 2990WX does win out.

The 2920X is actually the baby of the Threadripper 2 family, so it really has to compete on price/performance to be noticed. The thing is, except for the true multi-threaded workloads, the Ryzen 7 2700X is going to be the better day-to-day chip. It all depends on if the TR2 system is going to run as a standalone workhouse, or as a true day-to-day machine. As a workhouse, it’ll go beyond the 2700X for sure.

How about if we compare AMD 12-core 2920X to Intel’s 12-core 7920X ?

If we take out the obvious AVX-512 wins for the i9-7920X, the Intel chip loses performance in the compile and web tests, but gains performance in encoding and system tests. Overall, these chips are around the same, except for the retail pricing: With AMD, you save 45%. That’s a no-brainer, right?

On the results overall, we can see why these two chips were launched later in the year compared to the 16-core and 32-core parts. They are more cost effective, although the performance is in line with the cost. Between all of the Threadripper parts, first generation and second generation, our recommendation is still on the TR2 2950X.

AMD Related Reviews
Ryzen 7 2700X Review Threadripper 
1950X Review
Threadripper 2
2990WX Review
Best CPUs
ASUS X399 ROG
Zenith Extreme
ASRock X399 Pro
Gaming
GIGABYTE X399
Designare EX
X399 Overview
Gaming: F1 2018
Comments Locked

69 Comments

View All Comments

  • The Hardcard - Monday, October 29, 2018 - link

    I am not clear on this: can I get a 4-active-die TR for rendering and then turn off the 2 parasite dies when they are a disadvantage. Say make the 2990X operate as a 2950X with the same performance and power?

    I am not clear if that is what the dynamic local mode is offering. I’d like to be able to do that, whether there is an official AMD path, or if the community finds another way.
  • BikeDude - Monday, October 29, 2018 - link

    <blockquote>Please note, if you plan to share out the Compression graph, please include the Decompression one. Otherwise you’re only presenting half a picture.</blockquote>

    Many moons ago I made a request to internal IT to adopt 7-zip so that I could save on bandwidth whenever I needed to pull a largish database (this was several years before GDPR obviously).

    No go. It turned out that compressing the backups every night eats a lot of time. (decompressing these files was very fast regardless of setup) Well, actually they did use 7z.exe, but only as a normal zipper.

    So sometimes the only relevant part of the equation is the compression time. (I do plan on purchasing AMD regardless for my next upgrade)
  • GreenReaper - Wednesday, October 31, 2018 - link

    Use a threading-capable version of xz with the -T parameter so it uses all available threads and you'll find it flies on the default compression settings. It has a Windows version, too: https://tukaani.org/xz/
  • GreenReaper - Wednesday, October 31, 2018 - link

    Incidentally, you can probably run it something like xz < "input command" > output.xz, which should mean you don't actually have to write the dumps out, just the compressed version.
  • PaoDeTech - Monday, October 29, 2018 - link

    I need 13 cores and 26 threads. Now what? I returned the 32 cores 64 threads one since it could not run FAR CRY at 60fps. But boy could it blend! Sarcasm aside, I write multi-threaded server software and unless I code an infinite loop by mistake (I'm NOT admitting to it) I can never max out 8 threads before hitting I/O limitations (on NVMe PCIe disk). But I can see how some number crunching parallel software would go to town with it.
  • peevee - Wednesday, October 31, 2018 - link

    "I can never max out 8 threads before hitting I/O limitations (on NVMe PCIe disk)"

    Do you know these are IO limitations or do you assume this? Because lack of scaling after 8 threads does not mean IO limit at all. For example, if you write in Java/C#/Python/JS etc (heap-mandatory languages), or even use heap alloc/dealloc in critical thread sections in fast languages like C++, this is what you are going to get (heap mutex = no scalability). And this is just 1 of a thousand pitfalls of massive threading.
  • PaoDeTech - Thursday, November 1, 2018 - link

    No locks, every client call gets its own thread (REST- IIS -WebAPI -.NET "stateless" server - Entity Framework - SQL Server with read committed snapshot isolation). Async all the way down. Under load I can see the disk active >50% and write speed maxes out at 7 MB/s (Toshiba NVMe PCIe 1TB SSD M2). All processes running on the same PC (i7 6700k - 32GB RAM): server, test clients, SQL server. Plenty of free ram.
    Of course performance optimization is in the details and I was referring to a specific write intensive test case. My point is that parallel scaling is not easy and may stop sooner than expected (for many reasons). On the other hand, I can always use faster single thread performance...
  • 29a - Monday, October 29, 2018 - link

    Please replace EgoMark (3DPM) with something else, anything else.
  • danjw - Monday, October 29, 2018 - link

    Are there any motherboards out there that support the security features of the Threadripper platform?
  • SLVR - Monday, October 29, 2018 - link

    This review is a bit more useful: https://www.techspot.com/review/1737-amd-threadrip...

Log in

Don't have an account? Sign up now