Benchmarking Performance: 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.

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

FCAT is single threaded, however in this test the full 5.0 GHz did not kick in.

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

For a test that did have 5.0 GHz kick in, the 8086K takes the record in our Dolphin test.

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

On 3DPM, the 8086K shows that the 4.3 GHz all-core is on par with the 8700K.

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)

Despite the faster single core frequency, this DRAM-limited test seems to load up another core and stops the 8086K from reaching 5.0 GHz.

Agisoft Photoscan 1.3.3: 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.3.3 (Large) Total Time

Agisoft is variable threaded, but the 8086K is still a small stones throw from the 8700K.

Ambient Overclocking and Power Scaling Analysis Benchmarking Performance: CPU Rendering Tests
Comments Locked

111 Comments

View All Comments

  • ipkh - Monday, June 11, 2018 - link

    The multiplier chart doesn't make sense.
    The single core is 5Ghz, but Intel is quoting 4.7 Ghz all core and you're showing 4.4 identical to 8700K. I understand the base frequencies are the same, but the default multiplier for the 8086K should be higher. Is this a possible bios glitch or is the multiplier chart in the CPU not correct?
  • Hxx - Monday, June 11, 2018 - link

    Boost frequencies are all the same on 5 cores. there is a youtube video with somebody testing this chip on a z370 gaming 7 and you can clearly see in that video that boost is the same on all cores except 1. Intel = lame.
  • Ian Cutress - Monday, June 11, 2018 - link

    Where is Intel promoting 4.7 GHz all core?
  • HStewart - Monday, June 11, 2018 - link

    One thing that is strange is the name - the Original IBM PC that started this whole PC industry used the intel 8088 processor and not the Intel 8086 processor. The difference is that 8088 has 8 bit external and 8086 has 16 bit external - But CPU's used 16 bit internally. No internal Floating processor until the 386 line.

    But it wild that it been 40 years - I have an original IBM PC - in my downstairs closet, I remember while at Georgia Tech - putting a 2Meg Ram card into and booting up to 1.4Meg ramdisk and loading Microsoft C 3.0 compiler on it.

    As for new one - it would be cool if they actually included the original chip also as part of collectors edition.
  • AsParallel - Monday, June 11, 2018 - link

    8088 shipped in 79, was a variant of the 8086. 8086 was the first to 1M transistors
  • peevee - Monday, June 11, 2018 - link

    "No internal Floating processor until the 386 line."

    486. 386 still used 387 AFAIR. There were even 487, but it was just renamed 486 to be installed with 486SX.
  • HStewart - Monday, June 11, 2018 - link

    Yes I forgot that - the 486 was the one with Math Coprocessor.
  • AsParallel - Monday, June 11, 2018 - link

    Addition. The 8087 was the floating point coprocessor for the 8086/88
  • 29a - Monday, June 11, 2018 - link

    You didn't put 2mb of RAM in an original IBM PC it supported 256kb max.
  • HStewart - Monday, June 11, 2018 - link

    I had a special card in the PC - it was EMS memory - that could also fill up the main system memory to 640kb - instead of normal cache mode use by the card - I configured it as ram drive. Memory above 640Kb was directly accessible by the system.

Log in

Don't have an account? Sign up now