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

  • Lolimaster - Friday, August 11, 2017 - link

    Adding useless singe thread benchs for people that will pay $600+ for many cores is plain stupidity like that useless open a pdf test.
  • casperes1996 - Saturday, August 12, 2017 - link

    Why do you bother replying to these, Ian? I love your enthusiasm about what you do, and am happy that you reply to comments, but as you state yourself, no matter what you say, you'll be called a shill on more than a weekly basis by either side no matter what you do. Intel shill, AMD shill, Apple shill, Nvidia shill and so on. There's no stopping it, because you just can't please the people who go into something wanting a specific result. Well, you can if you give them that result, but sometimes, facts aren't what you want them to be, and some people don't accept that.

    Cheers, mate
  • Diji1 - Thursday, August 10, 2017 - link

    You sound like a crazy person.
  • Notmyusualid - Saturday, August 12, 2017 - link

    @ Diji1

    You are correct.

    He is implying just because we want HEDT platforms / chips, that we care nothing for single-threaded performance.

    He is a true AMD fan-boi, as you will see over time.
  • lordken - Thursday, August 10, 2017 - link

    @Johan Steyn: while I agree with you that the Intel piece with PR slide at the top was a little bit lame, I even lolled at "most scalable" part (isn't something like "glued" zen the most scalable design?) I think this review is good and goes also around architecture etc., there were few instances during reading when it seemed odd wording or being unnecessarily polite toward intel's shortcoming/deficit but I cant even remember them now.

    Though I was surprised about power numbers, as Toms measured much higher W for 7900X , 160-200 and with TTF even up to 250-331 , but here 7800/7900x had only ~150W.
    Also this sentence is odd
    "All the Threadripper CPUs hit around 177W, just under the 180W TDP, while the Skylake-X CPUs move to their 140W TDP." move to their? They are above the TDP...why not state it clearly?
  • tamalero - Thursday, August 10, 2017 - link

    Im sratching my head on power consumption as well. Almost all reviewers shows that the i9's consume more than threadripper.

    Could be the motherboard used?

    Some used the Zenith and other reviewers used the ASROCK retail one.
  • smilingcrow - Thursday, August 10, 2017 - link

    Power consumption can vary a lot depending on the type of task and the exact nature of that task.
    So you should expect a lot of variation across reviews.
  • Johan Steyn - Thursday, August 10, 2017 - link

    The amount of tests on games in this review is unbalanced. Also read my reply to Ian.

    Extremely well stated: " unnecessarily polite toward Intel's shortcoming" Sometimes I think these guys think all are complete mindless drones.
  • carewolf - Thursday, August 10, 2017 - link

    It has always been like this here. This was pretty neutral by Anandtech standards, they even admitted it when it was faster.
  • Johan Steyn - Thursday, August 10, 2017 - link

    Please read my response to Ian, I think you are not looking close enough to what is happening here.

Log in

Don't have an account? Sign up now