A Performance Review: AMD’s Ryzen 5 2600X & Ryzen 7 2700X Processors

Benchmarking a CPU may sound like a simple enough task, but in order to deliver accurate, repeatable results, and not to mention results that don’t favor one vendor over another, strict guidelines need to be adhered to. That in turn makes for rigorous, time-consuming testing, but we feel that the effort is worth it.

This page exists so that we can be open about how we test, and give those who care about testing procedures an opportunity to review our methodology before flaming us in the comments. Here, you can see a breakdown of all of our test machines, specifics about the tests themselves, and other general information that might be useful.

Let’s start with a look at the test platforms, for AMD’s TR4 and AM4, along with Intel’s LGA2011-v3, and LGA1151. We’re still in the process of benchmarking every relevant current-gen chip we have over, so for now, only nine CPUs are included in these results.

To prevent unexpected performance results, the “Multi-Core Enhancement” optimizations (effectively overclocking all cores to max turbo, instead of just two cores) offered by ASUS and GIGABYTE on their respective motherboards is disabled. There is, however, an exception. For Ryzen 2 testing, I had to use the DOCP profile on the motherboard to take proper advantage of the memory kit.

Since the other platforms were tested using 32GB of 3200MHz memory at 16-18-18, I had hoped that I’d be able to do the same here. Not so, at least with the kit I have here, and to be fair, that’s not a huge surprise since it’s not explicitly touting Ryzen support. That said, the Threadripper rig managed to use the kit just fine.

After much testing, I ultimately could run this same kit at the required speeds only if I had two sticks installed. As soon as the others were introduced, the system would simply not boot. Perhaps I could have worked around this by overclocking, but work had to get done, so I couldn’t spend time fiddling with that.

Just before I decided to use that configuration as-is for testing, a good friend reminded me that Ryzen kits are generally optimized for Ryzen for a reason, and that I should stick to an approved kit. That being the case, I decided to stick with the same kit AMD supplied with the Ryzen 2 reviewer kit, even though it bumps the speeds from 3200 to 3400. As much as I’d love to keep things apples-to-apples, it’s simply not possible that often where memory’s concerned.

That all said, here’s the test platforms:

Techgage’s CPU Testing Platforms

As tested configuration: AMD Ryzen Threadripper 1950X (Zen)

As tested configuration: AMD Ryzen Threadripper 1950X (Zen)

There’s not too much to say here, which is a good thing. While we didn’t find a huge difference to be made with the Core optimization left on (default), we disabled it to keep things as “reference” as possible. I truly dislike the EFI GIGABYTE has equipped on this board, as it’s pretty clunky, and in my opinion, disorganized. But, where it lacks in EFI polish, the board has made up for in stability.

As tested configuration: AMD Ryzen 7 2700X (Zen)

As tested configuration: AMD Ryzen 7 2700X (Zen)

As tested configuration: AMD Ryzen 5 2600X (Zen)

Nothing special had to be done on the Crosshair VII HERO to get up and running quickly. As covered above, I had to run with the DOCP Standard profile to get the memory to run at optimum settings. I’m not entirely sure if this means the CPU is slightly overclocked, because really, it’s hard to even tell nowadays given the tricks both motherboard and processor vendors employ.

Ultimately, my Cinebench scores came close to the reference results AMD supplied, so ultimately I feel pretty good that this platform is running as it should for any regular owner.

As tested configuration: Intel Core i9-7980XE (Skylake-X)

As tested configuration: Intel Core i9-7980XE (Skylake-X)

As tested configuration: Intel Core i9-7960X (Skylake-X)

As tested configuration: Intel Core i9-7960X (Skylake-X)

As tested configuration: Intel Core i9-7900X (Skylake-X)

As tested configuration: Intel Core i9-7900X (Skylake-X)

As tested configuration: Intel Core i7-7820X (Skylake-X)

As tested configuration: Intel Core i7-7820X (Skylake-X)

As tested configuration: Intel Core i7-7740X (Kaby Lake-X)

As tested configuration: Intel Core i7-7740X (Kaby Lake-X)

As with the TR4 platform, the Core “Enhancements” option is disabled on the LGA2011-v3 platform.

Windows Benchmarks

For the bulk of our testing, we use Windows 10 build 16299 with full updates as the base. After installation, LAN, audio, and chipset drivers are installed even if they are not explicitly needed (because Windows can use generic driver versions). Our basic guidelines beyond that are:

• Everything is disabled in “Customize settings” during OS install.
• 3D Vision and GeForce Experience are not installed with the graphics driver.
• Some services are disabled: search, User Account Control, Firewall, and Defender.
• The OneDrive app is changed to not start with Windows.
• The “Photos” app is removed, as it was found to hog CPU in the background
  PowerShell: Get-AppxPackage *photos* | Remove-AppxPackage
• The “Performance” power profile is used, with screen timeouts disabled.
• All notifications are disabled through the Settings screen.
• Desktop resolution is run at 2560×1440.
• Testing doesn’t begin until the PC is idle (keeps a steady minimum wattage).

Adobe Lightroom Classic CC: RAW to JPEG Export

Autodesk 3ds Max 2015: (SPECapc 3ds Max 2015)

Autodesk 3ds Max 2018: Fish Bowl Render (Arnold Renderer)

Adobe Premiere Pro CC 2018: Blu-ray Concert Encode

Adobe Premiere Pro CC 2018: 4K RED Encode

Adobe Premiere Pro CC 2018: 8K RED Encode

Blender: Agent 327 Render

Blender: Pavillon Render

Cinebench R15.038

dBpoweramp R15.1

POV-Ray 3.7

V-Ray Benchmark

SiSoftware Sandra 2017 SP3

• Media: Adobe Lightroom
• Media: Adobe Premiere Pro
• Rendering: Autodesk 3ds Max 2015 (SPECapc) & 3ds Max 2018
• Rendering: Blender
• Rendering: Cinebench
• Media: dBpoweramp
• Media: HandBrake
• Rendering: POV-Ray
• Rendering: V-Ray Benchmark
• System: SiSoftware Sandra 2017
  (Links go the benchmark result)

All of the tests shown above are used in their stock configuration. If you’re a Blender user and wish to compare your system’s performance to ours, you can download the project files for free here.

Gaming Benchmarks

Because the biggest bottleneck in a game is the graphics card, the workload needs to be put on the CPU as much as possible in order to better understand the raw performance scaling. As such, some of the games tested here were run at 1080p and 4K, with moderate detail levels.

Ashes of the Singularity Escalation: Benchmark Screenshot

Ashes of the Singularity Escalation: Game Settings

Grand Theft Auto V: Benchmark Screenshot

Grand Theft Auto V: Game Settings

Grand Theft Auto V: Game Settings

Grand Theft Auto V: Game Settings

Grand Theft Auto V: Game Settings

Total War 2: WARHAMMER II: Benchmark Screenshot

Total War 2: WARHAMMER II: Game Settings

Watch_Dogs 2: Benchmark Screenshot

Watch_Dogs 2: Game Settings

Watch_Dogs 2: Game Settings

• Synthetic: Ashes of the Singularity (CPU)
• Real-world: Grand Theft Auto V (CPU)
• Synthetic: Futuremark 3DMark (CPU + GPU)
• Synthetic: Total War: WARHAMMER II (CPU + GPU)
• Real-world: Watch_Dogs 2 (CPU + GPU)
  (Links go the benchmark result)

Because Ashes offers the ability to act only as a CPU benchmark, it makes sense to use that for a CPU performance article. GTA V isn’t very GPU intensive, leading us to see similar results at both 1080p and 4K. As such, only 1080p is used for that title. WARHAMMER II and Watch_Dogs 2 are tested at 4K, as well as 1080p.

Linux Benchmarks

Ubuntu 17.10 is the OS of choice for our test bed, as it’s both simple to set up, and so de facto that everyone reading the results should feel at home. The OS is left as stock as possible, with minor software added, and everything updated.

Before testing begins, we take the Phoronix Test Suite suggestion of enabling the “performance” power profile; something that actually improved the encode test by 15%-ish. The command run (sudo):

echo performance | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

Blender: Pavillon Render

GeekBench 4.0

Phoronix Test Suite 7.0

• Rendering: Blender
• Media: HandBrake
• System: Phoronix Test Suite
  (Links go the benchmark result)

Both the Blender and HandBrake tests are shared with the Windows testing. Phoronix Test Suite is used for the bulk of our Linux testing, as it supplies the tests we need, and makes them easy to use.

If you think there’s some information lacking on this page, or you simply want clarification on anything in particular, don’t hesitate to leave a comment.