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

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

Loading software is usually an achilles heel of multi-core processors based on the lower frequency. The 9980XE pushes above and beyond the 7980XE in this regard, given it has better turbo performance across the board.

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

Despite the 9980XE having a higher frequency than the 7980XE, they both fall in the same region as all these HEDT processors seems to be trending towards 48 seconds. For context, the 5.0 GHz Core i9-9900K scores 44.7 seconds, another 8% or so faster.

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

Without any AVX code, our 3DPM test shows that with fewer cores, AMD's 16-core Threadripper actually beats both of the 7980XE and 9980XE. The higher core count AMD parts blitz the field.

3D Particle Movement v2.1 (with AVX)

When we add AVX2 / AVX512, the Intel HEDT systems go above and beyond. This is the benefit of hand-tuned AVX512 code. Interestingly the 9980XE scores about the same as the 7980XE - I have a feeling that the AVX512 turbo tables for both chips are identical.

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

Dolphin enjoys single thread frequency, so at 4.5 GHz we see the 9980XE getting a small bump over the 7980XE.

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)

DigiCortex requires a good memory subsystem as well as cores and frequency. We get a small bump for the new 9980XE here.

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

With another one of our AVX2/AVX512 tests, the Skylake-X parts win in both single thread and multi-threads.

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

Photoscan is a mix of parallel compute and single threaded work, and the 9980XE does give another 7-8% performance over the 7980XE. The AMD dual-die TR2 parts still have the edge, however.

HEDT Performance: Rendering Tests HEDT Performance: Office Tests
Comments Locked

143 Comments

View All Comments

  • nadim.kahwaji - Tuesday, November 13, 2018 - link

    Niceeee , keep up the great work Ian ‘:)
  • AshlayW - Tuesday, November 13, 2018 - link

    In my opinion the entire Intel HEDT lineup is a joke. And the 9980XE: $180 more for literally just a bit over *half* the cores and threads. Sure it has better lightly threaded performance but surely that's not the intention of this processor, and surely it is not worth charging this insane 'Intel Tax' premium for it.
  • TEAMSWITCHER - Tuesday, November 13, 2018 - link

    Intel is free to charge whatever they want for a device that I have zero intention of purchasing. Most professionals I know have stopped using desktop computers for their daily drivers. The Dell XPS 15 and Apple's 15" MacBook Pro seam to be the weapons of choice these days. These products surely have their uses, but in the real world, most users are happy to sacrifice absolute performance for mobility.
  • imaheadcase - Tuesday, November 13, 2018 - link

    Most be a strange world you live on. Mobile won't ever be anything close to a desktop for daily tasks. I don't know any professional who have did that. They use mobile devices mainly to view items they did on desktop, not for working.
  • TEAMSWITCHER - Tuesday, November 13, 2018 - link

    Really? I work in software development (WEB, C++, OpenGL, and yes our own ray tracing engine) We have one guy with a desktop, the rest of the developers use either an XPS 15, a MacBook Pro, and one guy with a Surface Book. All were given a choice...this was the result.

    Interesting story about how we got here... Windows used to be a requirement for developing browser plugins. But with the move to Web Assembly, we can now compile and test our plugin on the Mac just as easily as we do on Windows. While many fanboys will lament this change .. I personally love it!

  • Endda - Tuesday, November 13, 2018 - link

    Yea, for code development only. Mobility has been the choice for that for years.

    Not everyone is a coder though. Some need these desktops for rendering big animations, videos, etc. You're simply not going to do that in any meaningful way on a laptop
  • PeachNCream - Tuesday, November 13, 2018 - link

    Rendering and production work can indeed happen on laptop hardware. I don't argue that desktop hardware with fewer limits on TDP and storage aren't a faster way to accomplish the same tasks, but as Team noted, given a choice, a lot of people opt for mobility over raw compute power.
  • nerd1 - Tuesday, November 13, 2018 - link

    It's a big joke to use XPS or Macbook GPU to do anything intensive. It's good for remote code editing though (except macbooks with absolute terrible keyboard)
  • TEAMSWITCHER - Tuesday, November 13, 2018 - link

    Define "intensive." Our software does real-time (WebGL) and photo-realistic (ray-tracing) rendering. I suppose that a Path Tracing engine would be MORE intensive. But the goal of our software is to be as ubiquitous as possible. We support the iPad and some Android tablets.
  • linuxgeex - Wednesday, November 14, 2018 - link

    There's your answer: anything that runs on iPad and Android Tablets is not "intensive". I'll grant you that it's "intensive" compared to what we were doing on workstations a decade ago, and mobile is closing the gap... but a workstation today has 24-56 cores (not threads) at 5Ghz and dual NVidia 2080 GPUs. You can get a 12-core CPU and dual 1080 in the pinnacle gaming laptops but they don't have ECC or the certifications of a workstation. At best they have half to 2/3 the performance. If you're paying your engineers by the hour you don't want them sitting on their hands twice as long. But I can see how they might make that choice for themselves. You make an excellent point there, lol.

Log in

Don't have an account? Sign up now