Benchmarking Suite 2017

2017 CPU

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. The 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.

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
Kraken
Octane
Web13
Web15

System Tests

PDF Opening
FCAT
3DPM v21
Dolphin v5.0
DigiCortex v1.20
Agisoft PS v1.0

Rendering Tests

Corona 1.3
Blender 2.78
LuxMark CPU C++
LuxMark CPU OpenCL
POV-Ray
CB15 ST
CB15 MT

Encoding Tests

7-Zip
WinRAR 5.4
TrueCrypt
HandBrake 264-LQ
HandBrake 264-HQ
HandBrake 265-4K

Office / Professional

PCMark8
Chromium Compile
SYSmark 2014 SE

Legacy Tests

3DPM v1 ST / MT
x264 HD 3 Pass 1, Pass 2
CB 11.5 ST / MT
CB 10 ST / MT

A side note - a couple of benchmarks (LuxMark) weren't fully 100% giving good data during testing. Need to go back and re-work this part of our testing.

2017 GPU

For our 2017 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, 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 special thing for the GTX 1080 here. The following tests are also added:

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

These two benchmarks, 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.

*A note on Ashes. During our initial testing, 8K and 16K testing were working great. But a game update around v.2.2 broke our scripting methods due to a new splashscreen/popup. We worked to find a solution that worked in order to start testing, however it still remains a kludge and the new resolution testing system stopped working. If it ever works again, we might start testing in 8K/16K.

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

264 Comments

View All Comments

  • rascalion - Monday, June 19, 2017 - link

    Are the Ryzen numbers in the charts retests using the last round of bios and software updates?
  • Ian Cutress - Monday, June 19, 2017 - link

    As much as possible, the latest BIOSes are used.
    Our CPU testing suite is locked in for software versions as of March 2017. This is because testing 30/50/100+ CPUs can't be done overnight, we have to have rigid points where versions are locked in. My cycle is usually 12-18 months. (Note I'm only one person doing all this data.)
  • FreckledTrout - Monday, June 19, 2017 - link

    Ian any chance once there are a few BIOS tweaks you could say do a mini updated review on the 7820x vs Ryzen 1800x. With Ryzen having latest BIOS as well plus 3200Mhz memory. I'm just curious really how the 8-core guys line up when some of the dust settles and I think a lot of people will be.
  • Ian Cutress - Monday, June 19, 2017 - link

    Any reason why 3200? I'll have Intel people saying it is pushing the Ryzen out of spec
  • jjj - Monday, June 19, 2017 - link

    You could do a memory subsystem scaling review for all platforms, Skylake X, Threadripper, Ryzen (Summit Ridge) and Coffee Lake. Cache, interconnect, DRAM. See where they are, how they scale, where the bottlenecks are, single rank vs dual rank modules and perf impact in practice.Why not even impact on power and efficiency.

    In any case, you'll need to update Ryzen 5 and 7 results when Ryzen 3 arrives , isn't it?

    For DRAM at 3200 it might be out of spec - overclocking the core is out of spec too but that has never stopped anyone from overclocking the memory. Right now 3200 is what a lot of folks buy , at least for higher end mainstream Ofc some will argue that Ryzen scales better with memory and that's why it is unfair but it's a hell of a lot more reasonable than testing 1080p gaming with a 1080 TI since it's a popular real world scenario.

    At the end of the day the goal should be to inform, not to watch out for Intel's or AMD''s feelings.
  • vanilla_gorilla - Monday, June 19, 2017 - link

    >For DRAM at 3200 it might be out of spec - overclocking the core is out of spec too but that has never stopped anyone from overclocking the memory.

    This. Exactly. We're enthusiasts and we always push the envelope. No one cares what the specs are all we care is about what these processors are capable of in the right hands.

    And Ian I think you guys do an awesome job, there's no other place I look for CPU benchmarks. Keep up what you do, we all appreciate it, as well as your willingness to have a dialog with us about the process. Really cannot say how impressed I am by how open and engaged you are, it's really commendable.
  • Ian Cutress - Tuesday, June 20, 2017 - link

    Thanks for the comments :)

    Though on your comments about pushing things out of spec. We have a good deal of readers who want plain stock for their businesses - AT isn't solely a consumer focused site. Otherwise I'd just jack all the CPUs and just post OC results :D Our base testing will always be at stock, and for comparison testing there has to be an element of consistency - testing an OC'ed part against a stock part in a direct A vs B comparison is only going to end up with a barrage of emails being rammed down my throat. There has to be some planning involved.
  • Ian Cutress - Tuesday, June 20, 2017 - link

    I've been planning a memory scaling article, I just haven't had the time (this article was around 6 weeks of prep with all the events going on that I had to attend).

    Note we don't retest stuff every review. With our new 2017 test suite, I've been going through regression testing. Usually regression testing is done once for the full segment until the benchmarks are changed again. I'll look at my next few months (still stupidly busy) and look at the priorities here.
  • FreckledTrout - Monday, June 19, 2017 - link

    Most people can easily buy a 3200 kit for not a lot of extra money. It doesn't take a lot tweaking(well not anymore on AGESA 1.0.0.6) or silicone lottery like an OC, just a bit more cash. From what I have seen with Ryzen it is the sweet spot on price and performance. I would assume Its likely the most chosen configuration on the R7's. To make it fair use 3200 on the 7820x as well. I only ask because Ryzen did way better than I would have thought and would like to see it with 3200Mhz memory and latest updates to see really how close Intel and AMD are on 8-core systems. Then im going to build :)
  • tipoo - Monday, June 19, 2017 - link

    Launch review! Nice work dude(s).

Log in

Don't have an account? Sign up now