AMD Zen 3 Ryzen Deep Dive Review: 5950X, 5900X, 5800X and 5600X Tested

Test Setup and #CPUOverload Benchmarks

As per our processor testing policy, we take a premium category motherboard suitable for the socket, and equip the system with a suitable amount of memory running at the manufacturer's maximum supported frequency. This is also typically run at JEDEC subtimings where possible. It is noted that some users are not keen on this policy, stating that sometimes the maximum supported frequency is quite low, or faster memory is available at a similar price, or that the JEDEC speeds can be prohibitive for performance. While these comments make sense, ultimately very few users apply memory profiles (either XMP or other) as they require interaction with the BIOS, and most users will fall back on JEDEC supported speeds - this includes home users as well as industry who might want to shave off a cent or two from the cost or stay within the margins set by the manufacturer. Where possible, we will extend out testing to include faster memory modules either at the same time as the review or a later date.

Many thanks to...

We must thank the following companies for kindly providing hardware for our multiple test beds. Some of this hardware is not in this test bed specifically, but is used in other testing.

Hardware Providers for CPU and Motherboard Reviews
Sapphire RX 460 Nitro	NVIDIA RTX 2080 Ti	Crucial SSDs	Corsair PSUs
G.Skill DDR4	ADATA DDR4	Silverstone Coolers	Noctua Coolers

-

The 2020 #CPUOverload Suite

Our CPU tests go through a number of main areas. We cover Web tests using our un-updateable version of Chromium, opening tricky PDFs, emulation, brain simulation, AI, 2D image to 3D model conversion, rendering (ray tracing, modeling), encoding (compression, AES, video and HEVC), office based tests, and our legacy tests (throwbacks from another generation of code but interesting to compare).

The Win10 Pro operating system is prepared in advance, and we run a number of registry edit commands again to ensure that various system features are turned off and disabled at the start of the benchmark suite. This includes disabling Cortana, disabling the GameDVR functionality, disabling Windows Error Reporting, disabling Windows Defender as much as possible again, disabling updates, and re-implementing power options and removing OneDrive, in-case it sprouted wings again.

A number of these tests have been requested by our readers, and we’ve split our tests into a few more categories than normal as our readers have been requesting specific focal tests for their workloads. A recent run on a Core i5-10600K, just for the CPU tests alone, took around 20 hours to complete.

Power

• Peak Power (y-Cruncher using latest AVX)
• Per-Core Loading Power using POV-Ray

Office

• Agisoft Photoscan 1.3: 2D to 3D Conversion
• Application Loading Time: GIMP 2.10.18 from a fresh install
• Compile Testing (WIP)

Science

• 3D Particle Movement v2.1 (Non-AVX + AVX2/AVX512)
• y-Cruncher 0.78.9506 (Optimized Binary Splitting Compute for mathematical constants)
• NAMD 2.13: Nanoscale Molecular Dynamics on ApoA1 protein
• AI Benchmark 0.1.2 using TensorFlow (unoptimized for Windows)

Simulation

• Digicortex 1.35: Brain stimulation simulation
• Dwarf Fortress 0.44.12: Fantasy world creation and time passage
• Dolphin 5.0: Ray Tracing rendering test for Wii emulator

Rendering

• Blender 2.83 LTS: Popular rendering program, using PartyTug frame render
• Corona 1.3: Ray Tracing Benchmark
• Crysis CPU-Only: Can it run Crysis? What, on just the CPU at 1080p? Sure
• POV-Ray 3.7.1: Another Ray Tracing Test
• V-Ray: Another popular renderer
• CineBench R20: Cinema4D Rendering engine

Encoding

• Handbrake 1.32: Popular Transcoding tool
• 7-Zip: Open source compression software
• AES Encoding: Instruction accelerated encoding
• WinRAR 5.90: Popular compression tool

Legacy

• CineBench R10
• CineBench R11.5
• CineBench R15
• 3DPM v1: Naïve version of 3DPM v2.1 with no acceleration
• X264 HD3.0: Vintage transcoding benchmark

Web

• Kraken 1.1: Depreciated web test with no successor
• Octane 2.0: More comprehensive test (but also deprecated with no successor)
• Speedometer 2: List-based web-test with different frameworks

Synthetic

• GeekBench 4 and GeekBench 5
• AIDA Memory Bandwidth
• Linux OpenSSL Speed (rsa2048 sign/verify, sha256, md5)
• LinX 0.9.5 LINPACK (where appropriate)

SPEC (Estimated)

• SPEC2006 rate-1T
• SPEC2017 rate-1T
• SPEC2017 rate-nT

It should be noted that due to the terms of the SPEC license, because our benchmark results are not vetted directly by the SPEC consortium, we have to label them as ‘estimated’. The benchmark is still run and we get results out, but those results have to have the ‘estimated’ label.

Others

• A full x86 instruction throughput/latency analysis
• Core-to-Core Latency
• Cache-to-DRAM Latency
• Frequency Ramping

Some of these tests also have AIDA power wrappers around them in order to provide an insight in the way the power is reported through the test.

2020 CPU Gaming (GPU) Benchmarks

In the past, we’ve tackled the GPU benchmark set in several different ways. We’ve had one GPU to multiple games at one resolution, or multiple GPUs take a few games at one resolution, then as the automation progressed into something better, multiple GPUs take a few games at several resolutions. However, based on feedback, having the best GPU we can get hold of over a dozen games at several resolutions seems to be the best bet.

Normally securing GPUs for this testing is difficult, as we need several identical models for concurrent testing, and very rarely is a GPU manufacturer, or one of its OEM partners, happy to hand me 3-4+ of the latest and greatest. In that aspect, over the years, I have to thank ECS for sending us four GTX 580s in 2012, MSI for sending us three GTX 770 Lightnings in 2014, Sapphire for sending us multiple RX 480s and R9 Fury X cards in 2016, and in our last test suite, MSI for sending us three GTX 1080 Gaming cards in 2018.

For our testing on the 2020 suite, we have secured three RTX 2080 Ti GPUs direct from NVIDIA. These GPUs have been optimized for with drivers and in gaming titles, and given how rare our updates are, we are thankful for getting the high-end hardware.  (It’s worth noting we won’t be updating to whatever RTX 3080 variant is coming out at some point for a while yet.)

On the topic of resolutions, this is something that has been hit and miss for us in the past. Some users state that they want to see the lowest resolution and lowest fidelity options, because this puts the most strain on the CPU, such as a 480p Ultra Low setting. In the past we have found this unrealistic for all use cases, and even if it does give the best shot for a difference in results, the actual point where you come GPU limited might be at a higher resolution. In our last test suite, we went from the 720p Ultra Low up to 1080p Medium, 1440p High, and 4K Ultra settings. However, our most vocal readers hated it, because even by 1080p medium, we were GPU limited for the most part.

So to that end, the benchmarks this time round attempt to follow the basic pattern where possible:

1. Lowest Resolution with lowest scaling, Lowest Settings
2. 2560x1440 with the lowest settings (1080p where not possible)
3. 3840x2160 with the lowest settings
4. 1920x1080 at the maximum settings

Point (1) should give the ultimate CPU limited scenario. We should see that lift as we move up through (2) 1440p and (3) 4K, with 4K low still being quite strenuous in some titles.

Point (4) is essentially our ‘real world’ test. The RTX 2080 Ti is overkill for 1080p Maximum, and we’ll see that most modern CPUs pull well over 60 FPS average in this scenario.

What will be interesting is that for some titles, 4K Low is more compute heavy than 1080p Maximum, and for other titles that relationship is reversed.

For integrated graphics testing, we use the (1) and (4) settings to see where the GPU lies with respect to CPU performance (1) as well as test to confirm just how close integrated graphics is to proper 1080p gaming (4).

So we have the following benchmarks as part of our script, automated to the point of a one-button run and out pops the results approximately 10 hours later, per GPU. Also listed are the resolutions and settings used.

Offline Games

1. Chernobylite, 360p Low, 1440p Low, 4K Low, 1080p Max
2. Civilization 6, 480p Low, 1440p Low, 4K Low, 1080p Max
3. Deus Ex: Mankind Divided, 600p Low, 1440p Low, 4K Low, 1080p Max
4. Final Fantasy XIV: 768p Min, 1440p Min, 4K Min, 1080p Max
5. Final Fantasy XV: 720p Standard, 1080p Standard, 4K Standard, 8K Standard
6. World of Tanks: 768p Min, 1080p Standard, 1080p Max, 4K Max

Online Games

1. Borderlands 3, 360p VLow, 1440p VLow, 4K VLow, 1080p Badass
2. F1 2019, 768p ULow, 1440p ULow, 4K ULow, 1080p Ultra
3. Far Cry 5, 720p Low, 1440p Low, 4K Low, 1080p Ultra
4. Gears Tactics, 720p Low, 4K Low, 8K Low 1080p Ultra
5. Grand Theft Auto 5, 720p Low, 1440p Low, 4K Low, 1080p Max
6. Red Dead Redemption 2, 384p Min, 1440p Min, 8K Min, 1080p Max
7. Strange Brigade DX12, 720p Low, 1440p Low, 4K Low, 1080p Ultra
8. Strange Brigade Vulkan, 720p Low, 1440p Low, 4K Low, 1080p Ultra

For each of the games in our testing, we take the frame times where we can (the two that we cannot are Chernobylite and FFXIV). For these games, at each resolution/setting combination, we run them for as many loops in a given time limit (often 10 minutes per resolution). Results are then taken as average frame rates and 95^th percentiles.

If there are any game developers out there involved with any of the benchmarks above, please get in touch at ian@anandtech.com. I have a list of requests to make benchmarking your title easier! I have a literal document I’ve compiled showing what would be ideal, best practices, who gets it correct and who gets it wrong, etc.

The other angle is DRM, and some titles have limits of 5 systems per day. This may limit our testing in some cases; in other cases it is solvable.