Conclusions: Faster Than Expected

When I started testing for this review, looking purely at the specification sheet, I was expecting AMD’s Threadripper Pro 3995WX to come in just behind the 3990X in most of our testing. The same amount of cores, the same TDP, but slightly lower on frequencies in exchange for double the memory channels and 8x the memory support (also Pro features). More often than not our processor comparisons are usually testing systems with identical memory systems, or we don’t consider that memory difference that major in most of our testing. After going through the end data for this review, it would appear that it makes more of a difference than we initially had thought.

In the tests that matter, most noticeably the 3D rendering tests, we’re seeing a 3% speed-up on the Threadripper Pro compared to the regular Threadripper at the same memory frequency and sub-timings. The core frequencies were preferential on the 3990X, but the memory bandwidth of the 3995WX is obviously helping to a small degree, enough to pull ahead in our testing, along with the benefit of having access to 8x of the memory capacity as well as Pro features for proper enterprise-level administration.

The downside of this comparison is the cost: the SEP difference is +$1500, or another 50%, for the Threadripper Pro 3995WX over the regular Threadripper 3990X. With this price increase, you’re not really paying +50% for the performance difference (ECC memory also costs a good amount), but the feature set. Threadripper Pro is aimed at the visual effects and rendering market, where holding 3D models in main memory is a key aspect of workflow speed as well as full-scene production. Alongside the memory capacity difference, having double the PCIe 4.0 lanes means more access to offload hardware or additional fast storage, also important tools in the visual effects space. Threadripper Pro falls very much into the bucket of 'if you need it, this is the option to go for'.

For our testing, we used the Lenovo Thinkstation P620, the first Threadripper Pro system available in the market, and we’ll have a full review on it shortly. The Thinkstation Pro systems are always well designed workstations with longevity and professional workloads in mind, enabling 280 W cooling with a fun heatsink but also additional custom DRAM fans, a unique motherboard with an easily removable power supply, and support and space for a number of add-in cards. Lenovo’s units, if you buy them individually from the website, are eye-wateringly expensive (+$12200 for the 64-core CPU, a +120% markup), and it is recommended that any design studio that wants to test or order these units should work through a local distributor.

AMD is set to push Threadripper Pro into the consumer and commercial markets beyond Lenovo later this quarter. We have already been in touch with local regional system integrators who are already examining their options based on the three Threadripper Pro motherboards set to be available in the market from ASUS, GIGABYTE, and Supermicro. We are expecting a range of options to be available, and most design studios are likely to order pre-built systems with a variety of air and liquid cooling.

What might confuse a few users is that AMD is launching Threadripper Pro into the major market now, right on the cusp of its next-generation EPYC launch in the next eight weeks. These new EPYC processors should afford a sizeable raw compute upgrade moving to Zen 3 cores, all while Threadripper Pro is on Zen 2. As we saw comparing TR Pro to EPYC in this review, both on Zen 2, in some circumstances it is the push up to 280 W where TR Pro gets the best performance, and a 280 W version of next-generation EPYC might seem more appealing to users looking at TR Pro today. What exactly AMD will launch for EPYC is unknown, whereas TR Pro on this generation is now a known performance factor that system integrators are building on for the workstation market. EPYC never really fit into the workstation market that easily, which is why TR Pro exists today.

We have heard some conflicting dates as to when exactly Threadripper Pro will come to the mass market beyond Lenovo, but they all fall within Q1. We have reached out to AMD in order to source the other processors for our testing.

CPU Tests: Simulation
Comments Locked

118 Comments

View All Comments

  • Oxford Guy - Friday, February 12, 2021 - link

    Bulldozer was indeed particularly awful. Abstract names like Xeon are generally less annoying than misapplied real-world names.
  • Qasar - Friday, February 12, 2021 - link

    too bad bulldozer and netburst were code names for the architecture, and not marketing names like xeon and threadripper.
  • GeoffreyA - Saturday, February 13, 2021 - link

    You're right, but even FX and Phenom were in poorer taste than Athlon, which was sheer gold, I'd say. Is Threadripper good or bad as a name? What I say, or anyone else here says, doesn't matter. Only from a survey can we get a better picture, and even there it's a reflection of popular opinion, a blunt instrument, often misled by the times.

    Is there a standard of excellence, a mode of naming so tuned to the genius of the language that it never changes? It's evident to everyone that "Interstellar" sounds better than "Invisible Invaders from Outer Space," but we could be wrong and time only can decide the matter. If, in 500 years, people still get a shiver when they hear Interstellar, we'll know that Nolan named his film right.

    Back to the topic. I think the spirit of Oxford Guy's comment was: TR and Epyc aren't that good names (which I partly agree with). Whether it inspires confidence in professionals is a different matter. A professional might be an expert in their field but it doesn't mean they're an expert on good names (and I'm not claiming I am one either). It matters little: if the target demographic buys, AMD's bank account smiles. But it's a fair question to ask, apart from sales, is a name good or bad? Which were the best? Does it sound beautiful?Names, in themselves, are pleasurable to many people.
  • jospoortvliet - Saturday, February 13, 2021 - link

    Names should have a few properties if they are to be good.
    Easy to pronounce (cross-culturally!)
    Easy to remember (distinctive)
    Not (too) silly/funny
    Bonus: have some (clever) relation to the actual product.

    Threadripper certainly earns the bonus but might arguably perhaps maybe lose out on the 3rd ‘silly’ point. However, in that regards i would argue it makes a difference how well it fulfills that rather ambitious title, and as we all know the answer is “very well”. Now if threadripper was a mediocre product, not at all living up to its name, I’d judge different but as it stands I would say it is a brilliant name.
  • GeoffreyA - Saturday, February 13, 2021 - link

    Good breakdown that, to test names against. Simplicity, too, wins the day.
  • GeoffreyA - Saturday, February 13, 2021 - link

    "Bulldozer was indeed particularly awful"

    One of the worst. AMD's place names were good in the K8 era, and the painter ones are doing a good job too.
  • danjw - Saturday, February 13, 2021 - link

    You may not be aware of this, but Threadripper, is actually comes from the 80's fashion fad of ripped clothing. ;-)
  • GeoffreyA - Saturday, February 13, 2021 - link

    Well, I like it even more then, being a fan of the 80s.
  • Hulk - Tuesday, February 9, 2021 - link

    Is the difference in output quality strictly due to rounding/numerical errors when using GPU vs CPU or are there differences in the computational algorithms that calculate the numbers?
  • Kjella - Tuesday, February 9, 2021 - link

    Not in terms of color accuracy, not a problem making 10/12 bit non-linear color from 32 bit linear - even 16 bit is probably near perfect. But for physics engines, ray tracing etc. errors can compound a lot - imagine a beam of light hitting a reflective surface where fractions of a degree means the light bounces in a completely different direction. Or you're modelling a long chain of events that cause compounding errors, or the sum of a million small effects or whatever. But it can also just be that the algorithms are a bit "lazy" and expect everything to fit because they got 64 bits to play with. I doubt that much needs ~1.0000000001 precision, much less ~1.0000000000000000001.

Log in

Don't have an account? Sign up now