AMD Threadripper 3990X CPU Review | Code Compile, Render, & Compression

We have a few other tests we still want to do with this CPU, but those will have to wait until we get home. We threw this one together just before leaving for Taiwan (in the final hours!) for factory tours, but it's still pretty complete. New code compile stuff will be fun as we expand it.
If you want to watch us lap/sand a Threadripper 3970X CPU, check out this video: https://www.youtube.com/watch?v=7WvD-_BSPps

14:56

Steve when compiling anything memory is king.

In a perfect world, a 3990x would use 128gb for compilers alone.

This is important – 1 THREAD 1 Gig of memory.

When compiling code, 2 things are key beyond the CPU Itself, one is rapid disks, you will (depending on the build) do a lot of disk thrashing, so SSD / NVMe, the second is
enough RAM to back it all, and even then from what i have learned so far, the 3990x is so heavily memory-constrained in workload using all 128 threads results in a slower build, using make -j 96 or equivalent gives a faster compile and uses just 96 gigs of ram.

If you have less than 1 gig per thread you'll find the system starts swapping to disk, and as soon as that shit starts its game over for performance, match the build commands to the system being used, and then a week it.

If like me you can afford it, strap 256 gigs of ram with it. Then go nuts on your benchmarking compiles.

Youll be amazed how hardcore the memory constraints are on the 3990, you simply cant feed it large amounts of data fast enough, as evidenced by

make -j 96 being about 20% faster than make -j 128

Good on you for mentioning Phoronix. Michael does great work on testing Linux distros for performance with recent hardware.

I'd wish Phoronix made YouTube videos. Would you consider doing a collab with him? Make sure to have some Bavarian beer at hand 😉

Freelance 3d animator here, with 20+ years in the medical device industry. I'll be harvesting some of my organs to pay for a 3990x plus 256GB of RAM. This will solve some major pain points I've been enduring for years!

@ 11:22 "intel's more commonly available "10980XE" what? Maybe to you reviewers. LMAO. Read the /r/intel subreddit or ask scan in the UK. June availability and that was BEFORE corona. That CPU is not more commonly available by any stretch of the imagination. It is in major shortage.

5:16 = Compile Benchmark

7:11 = Max Frequency 1T @ Cinebench R20
7:40 = Blender MultiThreaded Frequency
9:02 = Blender NT Thermals on TR4 360 CLC
10:10 = Blender GN CPU Benchmark (GN Logo)
12:01 = Blender GN CPU Benchmark (Monkey Head)
12:44 = Adobe Premiere Pro CC 2019 (1080p60)
13:47 = Adobe Premiere Pro CC 2019 (2160p60)
14:46 = 7-Zip 1806 x64 Compression
15:46 = 7-Zip 1806 x64 Decompression

That cat case and kitten gpu had me cracking the F up

Talking about travelling right now, to Taiwan no less, is beyond irresponsible and borderline evil. That on top of the cringeworthy cat shit … JFC people.

is it me or his voice sounds shit

You need to start including cfd applications fluent in your benchmark tests, am sure the benefits will be more visible

Pretty good review for a lady.

Welcome to the internets.

i WANT A i9 10980xe….
BUT WHERE ARE THEY!!@$!~

Compilation tasks usually require up to 2GB RAM per _thread_. So, 64GB RAM for 64 cores worked for Chromium, but can be too low for other C++ projects. Hopefully, 128 threads is too much for those many C++ projects in the wild because they just don't have so many independent compilation units to load all those threads at the same time. If some arbitrary compilation task "don't scale from 32 to 64 core", this probably not because hardware does not scale, but because the project itself just don't have enough number of independent compilation units to feed increased number of cores.

You don't do Server benchmarks, but the multi core CPUs all ask for virtualization, containerisations and multi-user use. That would be hard to benchmark but I think it is what all users of those chips are interested.

You should probably skip Workstation testing because the loads you have for them aren't shit. Without having demanding tasks, or figuring out how to multitask workloads, you can't even begin to show what something like a 64 core processor can do.

And all the overclocking stuff?????????????

I don't see many businesses buying a $4000 CPU for a system and then allowing it to be overclocked when these systems are typically having to be RELIABLE, and running for hours on end pushing heavy workloads.

It's just so unrealistic it's not worth the bother.

I know you guys might not see this but something to consider for rendering benchmarks is bucket/tile size. too big and you dont take enough advantage of many cores, too little and you create alot of bucket overhead, you might want to do some testing around this and find a sweet spot for your new methodology.
Also I know blender is free but its not exactly the most robust 3D app on the market, testing in 3ds max with vray might prove to use the resources better. The stand alone benchmark is a bit outdated at this point.
Keep up the good work guys,!

18:12 Summary

I just got a r3 1200 because my old laptop died and I cried a little watching this video.

Wait. So compiling Chromium takes three hours, 20 minutes?

this is for rich people only