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

  • Vorl - Thursday, August 10, 2017 - link

    the answer to both of you is that "this is a High end PC processor, not a workstation CPU, and not a server CPU. That was clearly covered at the start of the article.

    If you want raw number crunching info, there will be other sites that are going to have those reviews, and really, maybe anandtech will review it in that light since it really is such a powerful CPU in another review for server stuff.

    Also, there is a LOT of value in having a standardized set of tests. Even if a few tests here and there are no longer valuable like PDF opening, the same tests being used across the board are important for BENCH. you can't compare products if you aren't using the same tools.

    Unfortunately AMD is ahead of the curve currently with massive SMP being given to normal consumers now at a reasonable price. It will take a little time for dev's to catch up and really make use of this amazing CPU.

    With the processing power in a CPU like this imagine the game mechanics that can be created and used, For those of us that are more interested in making this a reasonably priced workstation/server build for VMs etc, cool for us, but that isn't where this is being marketed, and it's not really fair to jump all over the reviewer for it.
  • Zstream - Thursday, August 10, 2017 - link

    Utter rubbish. This CPU is designed for a workstation build. Some a product labeled Xeon is a workstation CPU, but this isn't?
  • mapesdhs - Friday, August 11, 2017 - link

    Yeah, TR doesn't really look like something that's massively aimed at gamers, it has too many capabilities and features which gamers wouldn't be interested in.
  • pm9819 - Friday, August 18, 2017 - link

    AMD themselves call it a consumer cpu. Is Intel paying them as well
  • Lolimaster - Friday, August 11, 2017 - link

    It's a HEDT/workstation, a year ago people called Workstation a dual Xeon 8 cores, which a sole 1950X replicates.

    Intel draws a line not supporting ECC, AMD supports ECC in all their main cpu's server or not all the way back to Athlon 64.

    16cores/32threads, ECC, 64 pci-e lanes, upgrade path to 32cores/64threads with zen3. Smells Workstation to me.

    Another thing is server cpu's which EPYC is, with features tailored to it, like a massive core count with low clock speeds to maximize efficiency and damn expensive mobos without any gamerish gizmo, just think to put on building without looking at net. TR can do a bit of that too, but optimized to an all around performance and budget friendly.
  • Ian Cutress - Thursday, August 10, 2017 - link

    Dan sums it up. Some of these tests are simply check boxes - is it adequate enough.

    Some people do say that an automated suite isn't the way to do things: unfortunately without spending over two months designing this script I wouldn't have time for nearly as much data or to test nearly as many CPUs. Automation is a key aspect to testing, and I've spent a good while making sure tests like our Chromium Compile can be process consistent across systems.

    There's always scope to add more tests (my scripts are modular now), if they can be repeatable and deterministic, but also easy to understand in how they are set up. Feel free to reach out via email if you have suggestions.
  • Johan Steyn - Thursday, August 10, 2017 - link

    Ian, I understand that you see them as checkboxes, but this is not a normal CPU John doe is going to buy. It has a very specific audience and I feel you are missing that audience badly. I guy that buys this to use for rendering or 3Dstudio Max, is not going to worry about games. Yes, it would be a great bonus to also be OK at it. Other sittes even did tests of running rendering as well as play games at the same time. TR shined like a star against Intel. This is actually something that might happen in real life. A guy could begin a render and then while waiting, decide to play a game.

    I would not buy TR to open pdf's, would I?
  • Ian Cutress - Thursday, August 10, 2017 - link

    No, but you open things like IDEs and Premiere. A PDF test is a gateway test in that regard with an abnormally large input. When a workstation is not crunching hard, it's being used to navigate through programs with perhaps the web and documents in tow where the UX is going to be indicative of something like PDF opening.
  • Lolimaster - Friday, August 11, 2017 - link

    Including useless benchs not only you waste target audience time, you too having to write and upload images from that useless benchs instead of making the article more interesting.

    How about a "the destroyer for HEDT/Workstion", a typical productivy load + some gaming, out of a sudden people will get TWICE the cpu resources, they can do things they couldn't before on the same machine.

    They could get a dual socket mobo with 2x10c Xeons paying the hefty premium with pathetic clock speeds if they wante to game a bit while doing work, TR fixed that, with mass consumer type of gaming performance while reducing the multicore costs by more than half (cores counts + ECC support without paying intel tax).
  • Lolimaster - Friday, August 11, 2017 - link

    And that audience few months ago was limited to do their productivity thing with 6-8 cores or 10 paying the huge intel tax, probably they couldn't game without hurting other things and had a 2 secondary PC for killing time.

    With TR and the massive 16 core count they can finally do all of that off a single PC or focus the entire powerhorse when they need (leaving things do work during their sleep).

Log in

Don't have an account? Sign up now