CPU Performance: System Tests

Our System Test section focuses significantly on real-world testing, user experience, with a slight nod to throughput. In this section we cover application loading time, image processing, simple scientific physics, emulation, neural simulation, optimized compute, and 3D model development, with a combination of readily available and custom software. For some of these tests, the bigger suites such as PCMark do cover them (we publish those values in our office section), although multiple perspectives is always beneficial. In all our tests we will explain in-depth what is being tested, and how we are testing.

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

For our graphs, some of them have two values: a regular value in orange, and one in red called 'Intel Spec'. ASUS offers the option to 'open up' the power and current limits of the chip, so the CPU is still running at the same frequency but is not throttled. Despite Intel saying that they recommend 'Intel Spec', the system they sent to us to test was actually set up with the power limits opened up, and the results they provided for us to compare to internally also correlated with that setting. As a result, we're providing both sets results for our CPU tests.

Application Load: GIMP 2.10.4

One of the most important aspects about user experience and workflow is how fast does a system respond. A good test of this is to see how long it takes for an application to load. Most applications these days, when on an SSD, load fairly instantly, however some office tools require asset pre-loading before being available. Most operating systems employ caching as well, so when certain software is loaded repeatedly (web browser, office tools), then can be initialized much quicker.

In our last suite, we tested how long it took to load a large PDF in Adobe Acrobat. Unfortunately this test was a nightmare to program for, and didn’t transfer over to Win10 RS3 easily. In the meantime we discovered an application that can automate this test, and we put it up against GIMP, a popular free open-source online photo editing tool, and the major alternative to Adobe Photoshop. We set it to load a large 50MB design template, and perform the load 10 times with 10 seconds in-between each. Due to caching, the first 3-5 results are often slower than the rest, and time to cache can be inconsistent, we take the average of the last five results to show CPU processing on cached loading.

AppTimer: GIMP 2.10.4

.

FCAT: Image Processing

The FCAT software was developed to help detect microstuttering, dropped frames, and run frames in graphics benchmarks when two accelerators were paired together to render a scene. Due to game engines and graphics drivers, not all GPU combinations performed ideally, which led to this software fixing colors to each rendered frame and dynamic raw recording of the data using a video capture device.

The FCAT software takes that recorded video, which in our case is 90 seconds of a 1440p run of Rise of the Tomb Raider, and processes that color data into frame time data so the system can plot an ‘observed’ frame rate, and correlate that to the power consumption of the accelerators. This test, by virtue of how quickly it was put together, is single threaded. We run the process and report the time to completion.

FCAT Processing ROTR 1440p GTX980Ti Data

.

3D Particle Movement v2.1: Brownian Motion

Our 3DPM test is a custom built benchmark designed to simulate six different particle movement algorithms of points in a 3D space. The algorithms were developed as part of my PhD., and while ultimately perform best on a GPU, provide a good idea on how instruction streams are interpreted by different microarchitectures.

A key part of the algorithms is the random number generation – we use relatively fast generation which ends up implementing dependency chains in the code. The upgrade over the naïve first version of this code solved for false sharing in the caches, a major bottleneck. We are also looking at AVX2 and AVX512 versions of this benchmark for future reviews.

For this test, we run a stock particle set over the six algorithms for 20 seconds apiece, with 10 second pauses, and report the total rate of particle movement, in millions of operations (movements) per second. We have a non-AVX version and an AVX version, with the latter implementing AVX512 and AVX2 where possible.

3DPM v2.1 can be downloaded from our server: 3DPMv2.1.rar (13.0 MB)

3D Particle Movement v2.1

.

3D Particle Movement v2.1 (with AVX)

.

Dolphin 5.0: Console Emulation

One of the popular requested tests in our suite is to do with console emulation. Being able to pick up a game from an older system and run it as expected depends on the overhead of the emulator: it takes a significantly more powerful x86 system to be able to accurately emulate an older non-x86 console, especially if code for that console was made to abuse certain physical bugs in the hardware.

For our test, we use the popular Dolphin emulation software, and run a compute project through it to determine how close to a standard console system our processors can emulate. In this test, a Nintendo Wii would take around 1050 seconds.

The latest version of Dolphin can be downloaded from https://dolphin-emu.org/

Dolphin 5.0 Render Test

.

DigiCortex 1.20: Sea Slug Brain Simulation

This benchmark was originally designed for simulation and visualization of neuron and synapse activity, as is commonly found 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, equivalent to a Sea Slug.

Example of a 2.1B neuron simulation

We report the results as the ability to simulate the data as a fraction of real-time, so anything above a ‘one’ is suitable for real-time work. Out of the two modes, a ‘non-firing’ mode which is DRAM heavy and a ‘firing’ mode which has CPU work, we choose the latter. Despite this, the benchmark is still affected by DRAM speed a fair amount.

DigiCortex can be downloaded from http://www.digicortex.net/

DigiCortex 1.20 (32k Neuron, 1.8B Synapse)

.

y-Cruncher v0.7.6: Microarchitecture Optimized Compute

I’ve known about y-Cruncher for a while, as a tool to help compute various mathematical constants, but it wasn’t until I began talking with its developer, Alex Yee, a researcher from NWU and now software optimization developer, that I realized that he has optimized the software like crazy to get the best performance. Naturally, any simulation that can take 20+ days can benefit from a 1% performance increase! Alex started y-cruncher as a high-school project, but it is now at a state where Alex is keeping it up to date to take advantage of the latest instruction sets before they are even made available in hardware.

For our test we run y-cruncher v0.7.6 through all the different optimized variants of the binary, single threaded and multi-threaded, including the AVX-512 optimized binaries. The test is to calculate 250m digits of Pi, and we use the single threaded and multi-threaded versions of this test.

Users can download y-cruncher from Alex’s website: http://www.numberworld.org/y-cruncher/

y-Cruncher 0.7.6 Single Thread, 250m Digitsy-Cruncher 0.7.6 Multi-Thread, 250m Digits

.

Agisoft Photoscan 1.3.3: 2D Image to 3D Model Conversion

One of the ISVs that we have worked with for a number of years is Agisoft, who develop software called PhotoScan that transforms a number of 2D images into a 3D model. This is an important tool in model development and archiving, and relies on a number of single threaded and multi-threaded algorithms to go from one side of the computation to the other.

In our test, we take v1.3.3 of the software with a good sized data set of 84 x 18 megapixel photos and push it through a reasonably fast variant of the algorithms, but is still more stringent than our 2017 test. We report the total time to complete the process.

Agisoft’s Photoscan website can be found here: http://www.agisoft.com/

Agisoft Photoscan 1.3.3, Complex Test

.

Our New Testing Suite for 2018 and 2019 CPU Performance: Rendering Tests
Comments Locked

136 Comments

View All Comments

  • johngardner58 - Monday, February 24, 2020 - link

    Again it depends on the need. If you need speed, there is no alternative. You can't get it by just running blades because not everything can be broken apart into independent parallel processes. Our company once ran an analysis that took a very long time. When time is money this is the only thing that will fill the bill for certain workloads. Having shared high speed resources (memory and cache) make the difference. That is why 255 Raspberry PIs clustered will not outperform most home desktops unless they are doing highly independent parallel processes. Actually the MIPS per watt on such a processor is probably lower than having individual processors because of the combined inefficiencies of duplicate support circuitry.
  • SanX - Friday, February 1, 2019 - link

    Every second home has few running space heaters 1500W at winter time
  • johngardner58 - Monday, February 24, 2020 - link

    Server side: depends on workload, usually yes a bladed or multiprocessor setup is usually better for massively parallel (independent) tasks, but cores can talk to each other much much much faster than blades, as they share caches, memory. So for less parallel work loads (single process multiple threads: e.g. rendering, numerics & analytics) this can provide far more performance and reduced costs. Probably the best example of the need for core count is GPU based processing. Intel also had specialized high core count XEON based accelerator cards with 96 cores at one point. There is a need even if limited.
  • Samus - Thursday, January 31, 2019 - link

    The problem is in the vast majority of the applications an $1800 CPU from AMD running on a $300 motherboard (that's an overall platform savings of $2400!) the AMD CPU either matches or beats the Intel Xeon. You have to cherry-pick the benchmarks Intel leads in, and yes, it leads by a healthy margin, but they basically come down to 7-zip, random rendering tasks, and Corona.

    Disaster strikes when you consider there is ZERO headroom for overclocking the Intel Xeon, where the AMD Threadripper has some headroom to probably narrow the gap on these few and far between defeats.

    I love Intel but wow what the hell has been going on over there lately...
  • Jimbo2K7 - Wednesday, January 30, 2019 - link

    Baby's on fire? Better throw her in the water!

    Love the Eno reference!
  • repoman27 - Wednesday, January 30, 2019 - link

    Nah, I figure Ian for more of a Die Antwoord fan. Intel’s gone zef style to compete with AMD’s Zen style.
  • Ian Cutress - Wednesday, January 30, 2019 - link

    ^ repoman gets it. I actually listen mostly to melodic/death metal and industrial. Something fast paced to help overclock my brain
  • WasHopingForAnHonestReview - Wednesday, January 30, 2019 - link

    My man
  • IGTrading - Wednesday, January 30, 2019 - link

    Was testing done with mediation regarding the specific windows BUG that affects AMD's CPUs with more than 16 cores? Or was it done with no attempt to ensure normal processing conditions for ThreadRipper, despite the known bug?
  • eva02langley - Thursday, January 31, 2019 - link

    Insomnium, Kalmah, Hypocrisy, Dark Tranquility, Ne Obliviscaris...

    By the way, Saor and Rotting Christ are releasing their albums in two weeks.

    You might want to check out Carpenter Brut - Leether Teeths and Rivers of Nihil - Where Owls Know My Name.

Log in

Don't have an account? Sign up now