The 2017 Benchmark Suite

For our review, we are implementing our fresh CPU testing benchmark suite, using new scripts developed specifically for this testing. This means that with a fresh OS install, we can configure the OS to be more consistent, install the new benchmarks, maintain version consistency without random updates and start running the tests in under 5 minutes. After that it's a one button press to start an 8-10hr test (with a high-performance core) with nearly 100 relevant data points in the benchmarks given below for CPUs, followed by our CPU gaming tests which run for 4-5 hours for each of the GPUs used. The CPU tests cover a wide range of segments, some of which will be familiar but some of the tests are new to benchmarking in general, but still highly relevant for the markets they come from.

Our new CPU tests go through six main areas. We cover the Web (we've got an un-updateable version of Chrome 56), general system tests (opening tricky PDFs, emulation, brain simulation, AI, 2D image to 3D model conversion), rendering (ray tracing, modeling), encoding (compression, AES, h264 and HEVC), office based tests (PCMark and others), and our legacy tests, throwbacks from another generation of bad code but interesting to compare.

All of our benchmark results can also be found in our benchmark engine, Bench.

A side note on OS preparation. As we're using Windows 10, there's a large opportunity for something to come in and disrupt our testing. So our default strategy is multiple: disable the ability to update as much as possible, disable Windows Defender, uninstall OneDrive, disable Cortana as much as possible, implement the high performance mode in the power options, and disable the internal platform clock which can drift away from being accurate if the base frequency drifts (and thus the timing ends up inaccurate).

Web Tests on Chrome 56

Sunspider 1.0.2
Mozilla Kraken 1.1
Google Octane 2.0
WebXPRT15

System Tests

PDF Opening
FCAT
3DPM v2.1
Dolphin v5.0
DigiCortex v1.20
Agisoft PhotoScan v1.0

Rendering Tests

Corona 1.3
Blender 2.78
LuxMark v3.1 CPU C++
LuxMark v3.1 CPU OpenCL
POV-Ray 3.7.1b4
Cinebench R15 ST
Cinebench R15 MT

Encoding Tests

7-Zip 9.2
WinRAR 5.40
AES Encoding (TrueCrypt 7.2)
HandBrake v1.0.2 x264 LQ
HandBrake v1.0.2 x264-HQ
HandBrake v1.0.2 HEVC-4K

Office / Professional

PCMark8
Chromium Compile (v56)
SYSmark 2014 SE

Legacy Tests

3DPM v1 ST / MT
x264 HD 3 Pass 1, Pass 2
Cinebench R11.5 ST / MT
Cinebench R10 ST / MT

CPU Gaming Tests

For our new set of GPU tests, we wanted to think big. There are a lot of users in the ecosystem that prioritize gaming above all else, especially when it comes to choosing the correct CPU. If there's a chance to save $50 and get a better graphics card for no loss in performance, then this is the route that gamers would prefer to tread. The angle here though is tough - lots of games have different requirements and cause different stresses on a system, with various graphics cards having different reactions to the code flow of a game. Then users also have different resolutions and different perceptions of what feels 'normal'. This all amounts to more degrees of freedom than we could hope to test in a lifetime, only for the data to become irrelevant in a few months when a new game or new GPU comes into the mix. Just for good measure, let us add in DirectX 12 titles that make it easier to use more CPU cores in a game to enhance fidelity.

Our original list of nine games planned in February quickly became six, due to the lack of professional-grade controls on Ubisoft titles. If you want to see For Honor, Steep or Ghost Recon: Wildlands benchmarked on AnandTech, please point Ubisoft Annecy or Ubisoft Montreal in my direction. While these games have in-game benchmarks worth using, unfortunately they do not provide enough frame-by-frame detail to the end user, despite using it internally to produce the data the user eventually sees (and it typically ends up obfuscated by another layer as well). I would instead perhaps choose to automate these benchmarks via inputs, however the extremely variable loading time is a strong barrier to this.

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

  • Civilization 6 (1080p Ultra, 4K Ultra)
  • Ashes of the Singularity: Escalation* (1080p Extreme, 4K Extreme)
  • Shadow of Mordor (1080p Ultra, 4K Ultra)
  • Rise of the Tomb Raider #1 - GeoValley (1080p High, 4K Medium)
  • Rise of the Tomb Raider #2 - Prophets (1080p High, 4K Medium)
  • Rise of the Tomb Raider #3 - Mountain (1080p High, 4K Medium)
  • Rocket League (1080p Ultra, 4K Ultra)
  • Grand Theft Auto V (1080p Very High, 4K High)

For each of the GPUs in our testing, these games (at each resolution/setting combination) are run four times each, with outliers discarded. Average frame rates, 99th percentiles and 'Time Under x FPS' data is sorted, and the raw data is archived.

The four GPUs we've managed to obtain for these tests are:

  • MSI GTX 1080 Gaming X 8G
  • ASUS GTX 1060 Strix 6G
  • Sapphire Nitro R9 Fury 4GB
  • Sapphire Nitro RX 480 8GB

In our testing script, we save a couple of special things for the GTX 1080 here. The following tests are also added:

  • Civilization 6 (8K Ultra, 16K Lowest)

This benchmark, with a little coercion, are able to be run beyond the specifications of the monitor being used, allowing for 'future' testing of GPUs at 8K and 16K with some amusing results. We are only running these tests on the GTX 1080, because there's no point watching a slideshow more than once.

*As an additional to this review, we do not have any CPU gaming data on Skylake-X. We ran a set of tests before Threadripper arrived, but now having had a chance to analyze the data, despite being on the latest BIOS and setup, there are still issues with performance that we need to nail down once this review is out of the way.

Test Bed and Setup Benchmarking Performance: CPU System Tests
Comments Locked

347 Comments

View All Comments

  • sorten - Friday, August 11, 2017 - link

    Swole? Threadripped?
  • Rottie - Friday, August 11, 2017 - link

    AMD Ryzen CPU is not fast enough. Apple is not ready for AMD Ryzen CPU, sorry AMD. I love AMD but I hated Intel even though I have a Skylake based MacBook Pro. :(
  • Deshi! - Friday, August 11, 2017 - link

    One small correction, Ryzen has 24 PCIE lanes, not 16. it has 16 for graphics only, but saying only 16 may make people (like me) wonder if you can't run an NVME at x4 and still have the graphics card at 16x, which you totally can do.
  • Deshi! - Friday, August 11, 2017 - link

    This is under Feeding the beast section btw, where you said "Whereas Ryzen 7 only had 16 PCIe lanes, competing in part against CPUs from Intel that had 28/44 PCIe lanes,"
  • fanofanand - Tuesday, August 15, 2017 - link

    He already answered this question/statement to someone else. there are 20 lanes from the CPU, 16 of which are available for graphics. I don't think his way of viewing it seems accurate, but he has stated that this is how PCIe lanes have been counted "for decades"
  • WaltC - Friday, August 11, 2017 - link

    Nice review, btw! Yes, going all the way back to Athlon and the triumph of DDR-Sdram over Rdram, and the triumph of AMD's x86-64 over Itanium (Itanium having been Intel's only "answer" for 64-bit desktop computing post the A64 launch--other than to have actually paid for and *run* an Intel ad campaign stating "You don't need 64-bits on the desktop", believe it or not), and going all the way back to Intel's initial Core 2 designs, the products that *actually licensed x86-64 from AMD* (so that Intel could compete in the 64-bit desktop space it claimed didn't exist), it's really remarkable how much AMD has done to enervate and energize the x86 computing marketplace globally. Interestingly enough it's been AMD, not Intel, that has charted the course for desktop computing globally--and it goes all the way back to the original AMD Athlon. The original Pentium designs--I owned 90MHz and 100MHz Pentiums before I moved to AMD in 1999--were the high-point of an architecture that Intel would *cancel* shortly thereafter simply because it could not compete with the Athlon and its spin-off architectures like the A64. That which is called "Pentium" today is not...;) Intel simply has continued to use the brand. All I can say is: TGF AMD...;) I've tried to imagine where Intel would have taken the desktop computing market had consumers allowed the company to lead them around by the nose, and I can't...;) If not for AMD *right now* and all the activity the company is bringing to the PC space once again, there would not be much of a PC market globally going on. But now that we have some *action* again and Intel is breaking its legs trying to keep up, the PC market is poised to break out of the doldrums! I guess Intel had decided to simply nap for a few decades--"Wake me when some other company does something we'll have to compete with!" Ugh.
  • zeroidea - Friday, August 11, 2017 - link

    Hi Ian,
    On the Civ 6 benchmark page, all results after the GTX 1080 are mislabeled as GTA 6.
  • Ahmad Rady - Friday, August 11, 2017 - link

    Can you try to test this CPU using windows server?
    This is a MCM CPU looks like 4 CPUs attached to each other.
    I think windows 10 Pro can't get the most of this CPU unless we have windows 10 Pro for WS
  • Pekish79 - Friday, August 11, 2017 - link

    Vray has a Rendering Benchmark too maybe you could use both
  • Pekish79 - Friday, August 11, 2017 - link

    I went to check both page of Vray and Corona Benchmark

    Corona match more or less the graphic and Vray has the following

    AMD 1950 : 00:46-00:48 sec
    I9 7900: 00:54-00:56 sec
    I7 6950: 01:00-01:10 sec
    I5 5960: 01:23-01:33 sec

Log in

Don't have an account? Sign up now