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

  • imaheadcase - Thursday, August 10, 2017 - link

    So you lost respect for a website based on how they word titles of articles? I think you don't understand advertising at all. lol

    If you want to know a website that lost respect, look at HardOCP and you know why people don't like them for obvious reasons.
  • Alexey291 - Thursday, August 10, 2017 - link

    No offence but HardOCP is far more respectable than what we have in ATech these days.

    But that's not hard. AT website is pretty much a shell for the forum which is where most of the traffic is. I'm sure they only so the reviews because 'it was something we have always done'
  • Johan Steyn - Thursday, August 10, 2017 - link

    You may not understand how wording is used to convey sentiments in a different way. That is what politicians thrive on. You could for instance say "I am sorry that you misunderstood me." It gives the impression that you are sorry, but you are not. People also ask for forgiveness like this: "If I have hurt you, please forgive me." It sounds sincer, but it is a hidden lie, not acknowledging that you have actually hurt anybody, actually saying that you do not think that you did.

    Well, this is a science and I cannot explain it all here. If you miss it, then it does not mean it is not there.
  • mikato - Monday, August 14, 2017 - link

    I thought I'd just comment to say I understand what you're saying and agree. Even if a sentence gives facts, it can sound more positive one way or another way based on how it is stated. The author has to do some reflection sometimes to catch this. I believe him whenever he says he doesn't have much time, and maybe that plays into it. But articles at different sites may not have this bias effect and it can be an important component of a review article.

    "Intel recently announced that its new 18-core chip scores 3200 on Cinebench R15. That would be an extra 6.7% performance over the Threadripper 1950X for 2x the cost."

    These 2 sentences give facts, but sound favorable to Intel until just the very end. It's a subtle perception thing but it's real. The facts in the sentences, however, are massively favorable to AMD. Threadripper does only 6.7% less performance than an announced (not yet released) Intel CPU for half the cost!

    Here is another version-

    "Intel recently announced that its new 18-core chip scores 3200 on Cinebench R15. So Threadripper, for half the cost of Intel's as-yet unreleased chip, performs only 6.7% slower in Cinebench."

    There, that one leads with Threadripper and "half the cost" in the second sentence, and sounds much different.
  • Johan Steyn - Thursday, August 10, 2017 - link

    HardOCP and PCPer is more respected in my opinion. Wccftech is unpredictable, sometimes they shine and sometimes they are really odd.
  • mapesdhs - Thursday, August 10, 2017 - link

    I've kinda taken to GamersNexus recently, but I still always read AT and toms to compare.

    Ian.
  • fanofanand - Tuesday, August 15, 2017 - link

    WCCFtech is a joke, it's nothing but rumors and trolling. If you are seriously going to put WCCFtech above Anandtech then everyone here can immediately disregard all of your comments.
  • Drumsticks - Thursday, August 10, 2017 - link

    Fantastic review In. I was curious exactly how AMD would handle the NUMA problem with Threadripper. It seems that anybody buying Threadripper for real work is going to have to continue being very aware of exactly what configuration gets them the best performance.

    One minor correction, at the bottom of the CPU Rendering tests page:

    "Intel recently announced that its new 18-core chip scores 3200 on Cinebench R15. That would be an extra 6.7% performance over the Threadripper 1950X for 2x the cost." - this score is for the 16 core i9-7960X, not the 7980XE.
  • Drumsticks - Thursday, August 10, 2017 - link

    Ian*. Can't wait for the edit button one day!
  • launchcodemexico - Thursday, August 10, 2017 - link

    Why did you end all the gaming review sections with something like "Switching it to Game mode would have made better numbers..."? Why didn't you run the benchmarks in Gaming mode in the first place?

Log in

Don't have an account? Sign up now