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

  • Pekish79 - Friday, August 11, 2017 - link

    Vraybench 1.0.5
  • SanX - Friday, August 11, 2017 - link

    *** AMD, make 2-chip mobos for upcoming multicore wars, you will double your profit from this at no cost for you +++
  • vicbee - Friday, August 11, 2017 - link

    Off subject: Having just read the article about nVidia's meteoric rise in profits, some of which directly attributed to high end "gamers" video cards purchased expressly for coin mining, I wonder if it and AMD are going to manufacture CPU's and GPU's specifically for that purpose and how that will affect the price of said parts...
  • Avro Arrow - Friday, August 11, 2017 - link

    Hi Ian, thanks for doing this article. It's important to see all possible outcomes because in the real world, anything is possible. I do have one question that has be puzzled. Why do you say that Threadripper only has 64 PCI-Express 3.0 lanes when it's been reported several times by everyone, including official AMD releases (and also including by you) that it has 64? I thought it might be just a typo but you state it in several places and in all of your specs. This is not a new thing so is there something about Threadripper that we don't know?
  • HotJob - Friday, August 11, 2017 - link

    Could someone explain to me what a "2P" system is from the competition section of the article?
  • coolhardware - Saturday, August 12, 2017 - link

    "2P" system = two processor system, i.e. a system with two physical CPU sockets and two CPUs installed.

    In the past a 2P (or 4P) system was really handy to get more cores especially back when 1 core, 2 core, and eventually 4 core CPUs were high end. In the consumer realm, way back, the Pentium II was the first 2P system I ever built and people even did it with Celerons as well:
    http://www.cpu-central.com/dualceleron/
    the Opterons were also fun for dual or quad processor systems including some SFF options like the ZMAX-DP socket 940 system.
    https://www.newegg.com/Product/Product.aspx?Item=N...

    Now fast forward with ThreadRipper already available at Amazon and NewEgg
    http://amzn.to/2wDqgWw (URL shortened)
    https://www.newegg.com/Product/Product.aspx?Item=N...
    I do not think I will ever be building a 2P or 4P system again!!!

    :-)
  • rvborgh - Friday, August 11, 2017 - link

    hi Ian,

    i think the Cinebench 11.5 benchmarks are incorrect for both ThreadRippers. ThreadRipper is almost equivalent to my Quad Opteron (48 core) system which scores 3229cb on R15... and 39.04 on Cinebench 11.5. if i downclock all cores to approximately 2.9 GHz i end up with around 3000cb in R15 and in the 36 range point range for 11.5.

    The fact that you are only scoring in the 18 range makes me wonder if you had the Threadripper set in some mode where it was only using 8 out of the 16 cores. Can you verify this... please? Thanks :) i would think you should see scores in the 36 range with 11.5.

    Other than this minor detail... great article.

    PS: i've had the same issues with software not liking NUMA on my quad opteron system as well... Cinebench especially does not like it.
  • Tchamber - Saturday, August 12, 2017 - link

    Hi, Ian. Thanks for the review. As usual it was in depth and informative. I'm in the middle of building a 1700x system now based on your review. I wanted to say you handle all the nay-Sayers, gloomy Gusses and negative Nacies with aplomb! I think most people's own slant colors how they see your reviews. I appreciate the consistency of what you do here. I took a look over at Ars, and they could be called AMD shills for all the positive things they say... Keep it up!
  • Tchamber - Saturday, August 12, 2017 - link

    P.S.
    I loved your Kessel Run reference, it tied in nicely with your Yoda quote.
  • B3an - Saturday, August 12, 2017 - link

    Too many plebs complaining about a lack of 3D rendering benches. The fact is a 16 core CPU is still much slower than GPU's at rendering. I'll be getting a 1950X but it wont even be used for rendering when i know for a fact that my two GPUs will still be much faster with things like Blender. Even a single high-end GPU will still easily beat the 1950X at these tasks.

    Seems like immature moron fanboys are crying over this stuff because they just want to see AMD at the top of the charts.

Log in

Don't have an account? Sign up now