CPU System Tests

Our first set of tests is our general system tests. These set of tests are meant to emulate more about what people usually do on a system, like opening large files or processing small stacks of data. This is a bit different to our office testing, which uses more industry standard benchmarks, and a few of the benchmarks here are relatively new and different.

All of our benchmark results can also be found in our benchmark engine, Bench.

PDF Opening

First up is a self-penned test using a monstrous PDF we once received in advance of attending an event. While the PDF was only a single page, it had so many high-quality layers embedded it was taking north of 15 seconds to open and to gain control on the mid-range notebook I was using at the time. This put it as a great candidate for our 'let's open an obnoxious PDF' test. Here we use Adobe Reader DC, and disable all the update functionality within. The benchmark sets the screen to 1080p, opens the PDF to in fit-to-screen mode, and measures the time from sending the command to open the PDF until it is fully displayed and the user can take control of the software again. The test is repeated ten times, and the average time taken. Results are in milliseconds.

System: PDF Opening with Adobe Reader DC

This opening test is single threaded, so the high-frequency Intel parts get a clear win. There's not much between the Threadripper CPUs here.

FCAT Processing: link

One of the more interesting workloads that has crossed our desks in recent quarters is FCAT - the tool we use to measure and visually analyze stuttering in gaming due to dropped or runt frames. The FCAT process requires enabling a color-based overlay onto a game, recording the gameplay, and then parsing the video file through the analysis software. The software is mostly single-threaded, however because the video is basically in a raw format, the file size is large and requires moving a lot of data around. For our test, we take a 90-second clip of the Rise of the Tomb Raider benchmark running on a GTX 980 Ti at 1440p, which comes in around 21 GB, and measure the time it takes to process through the visual analysis tool.

System: FCAT Processing ROTR 1440p GTX980Ti Data

Similar to PDF opening, single threaded performance wins out.

Dolphin Benchmark: link

Many emulators are often bound by single thread CPU performance, and general reports tended to suggest that Haswell provided a significant boost to emulator performance. This benchmark runs a Wii program that ray traces a complex 3D scene inside the Dolphin Wii emulator. Performance on this benchmark is a good proxy of the speed of Dolphin CPU emulation, which is an intensive single core task using most aspects of a CPU. Results are given in minutes, where the Wii itself scores 17.53 minutes.

System: Dolphin 5.0 Render Test

Dolphin likes single thread performance as well, although having some cores to back it up seems to be required. 

3D Movement Algorithm Test v2.1: link

This is the latest version of the self-penned 3DPM benchmark. The goal of 3DPM is to simulate semi-optimized scientific algorithms taken directly from my doctorate thesis. Version 2.1 improves over 2.0 by passing the main particle structs by reference rather than by value, and decreasing the amount of double->float->double recasts the compiler was adding in. It affords a ~25% speed-up over v2.0, which means new data.

System: 3D Particle Movement v2.1

Our first pure multithreaded test, and the 1950X wins with 32 threads. The 1920X beats the 1950X in SMT-off mode, due to 24 threads beating 16 threads.

DigiCortex v1.20: link

Despite being a couple of years old, the DigiCortex software is a pet project for the visualization of neuron and synapse activity in the brain. The software comes with a variety of benchmark modes, and we take the small benchmark which runs a 32k neuron/1.8B synapse simulation. The results on the output are given as a fraction of whether the system can simulate in real-time, so anything above a value of one is suitable for real-time work. The benchmark offers a 'no firing synapse' mode, which in essence detects DRAM and bus speed, however we take the firing mode which adds CPU work with every firing.

System: DigiCortex 1.20 (32k Neuron, 1.8B Synapse)

DigiCortex requires a mash of CPU frequency and DRAM performance to get a good result, and anything with quad-channel memory is usually preferred. The 1950X in SMT-off mode wins here due to its low main memory latency combined with having 16 threads to access it. The Broadwell-E is the nearest competitor, over Skylake-X, most likely due to the mesh vs ring topology. The 1950X in Creator mode scores way down the field however, lower than the standard Ryzen chips, showing that under a unified memory architecture there can be significant performance drops. The 1920X failed in this test for an unknown reason.

Agisoft Photoscan 1.0: link

Photoscan stays in our benchmark suite from the previous version, however now we are running on Windows 10 so features such as Speed Shift on the latest processors come into play. The concept of Photoscan is translating many 2D images into a 3D model - so the more detailed the images, and the more you have, the better the model. The algorithm has four stages, some single threaded and some multi-threaded, along with some cache/memory dependency in there as well. For some of the more variable threaded workload, features such as Speed Shift and XFR will be able to take advantage of CPU stalls or downtime, giving sizeable speedups on newer microarchitectures.

System: Agisoft Photoscan 1.0 Total Time

The variable threaded nature of Agisoft shows that in our workflow, it's a mix of cores, IPC and frequency required to win. AMD takes a back seat here, likely due to its AVX implementation.

The 2017 Benchmark Suite Benchmarking Performance: CPU Rendering 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