CPU Tests: SPEC

Page by Andrei Frumusanu

SPEC2017 is a series of standardized tests used to probe the overall performance between different systems, different architectures, different microarchitectures, and setups. The code has to be compiled, and then the results can be submitted to an online database for comparison. It covers a range of integer and floating point workloads, and can be very optimized for each CPU, so it is important to check how the benchmarks are being compiled and run.

We run the tests in a harness built through Windows Subsystem for Linux, developed by our own Andrei Frumusanu. WSL has some odd quirks, with one test not running due to a WSL fixed stack size, but for like-for-like testing is good enough. Because our scores aren’t official submissions, as per SPEC guidelines we have to declare them as internal estimates from our part.

For compilers, we use LLVM both for C/C++ and Fortan tests, and for Fortran we’re using the Flang compiler. The rationale of using LLVM over GCC is better cross-platform comparisons to platforms that have only have LLVM support and future articles where we’ll investigate this aspect more. We’re not considering closed-sourced compilers such as MSVC or ICC.

clang version 10.0.0
clang version 7.0.1 (ssh://git@github.com/flang-compiler/flang-driver.git
 24bd54da5c41af04838bbe7b68f830840d47fc03)

-Ofast -fomit-frame-pointer
-march=x86-64
-mtune=core-avx2
-mfma -mavx -mavx2

Our compiler flags are straightforward, with basic –Ofast and relevant ISA switches to allow for AVX2 instructions. We decided to build our SPEC binaries on AVX2, which puts a limit on Haswell as how old we can go before the testing will fall over. This also means we don’t have AVX512 binaries, primarily because in order to get the best performance, the AVX-512 intrinsic should be packed by a proper expert, as with our AVX-512 benchmark. All of the major vendors, AMD, Intel, and Arm, all support the way in which we are testing SPEC.

To note, the requirements for the SPEC licence state that any benchmark results from SPEC have to be labeled ‘estimated’ until they are verified on the SPEC website as a meaningful representation of the expected performance. This is most often done by the big companies and OEMs to showcase performance to customers, however is quite over the top for what we do as reviewers.

For the new Cypress Cove based i7-11700K, we haven’t had quite the time to investigate the new AVX-512 instruction differences – since this is the first consumer desktop socketed CPU with the new ISA extensions it’s something we’ll revisit in the full review. Based on our testing on the server core counterparts however, it doesn’t make any noticeable differences in SPEC.

SPECint2017 Rate-1 Estimated Scores

In the SPECint2017 suite, we’re seeing the new i7-11700K able to surpass its desktop predecessors across the board in terms of performance. The biggest performance leap is found in 523.xalancbmk which consists of XML processing at a large +54.4% leap versus the 10700K.

The rest of the improvements range in the +0% to +15% range, with an average total geomean advantage of +15.5% versus the 10700K. The IPC advantage should be in the +18.5% range.

SPECfp2017 Rate-1 Estimated Scores

In the FP scores, there’s nothing standing out too much, with general even improvements across the board. The total improvement here is +19.6%, with the IPC improvement in the +22% range.

SPEC2017 Rate-1 Estimated Total

Although the new Cypress Cove cores in the 11700K do have good generational IPC improvements, that’s all compared to the quite old predecessor, meaning that for single-thread performance, the advancements aren’t enough to quite keep up with the latest Zen3 competition from AMD, or for that matter, the Firestorm cores in Apple’s new M1.

SPEC2017 Rate-N Estimated Total

More interesting are the multi-threaded SPEC results. Here, the new generation from Intel is showcasing a +5.8% and +16.2% performance improvement over its direct predecessor. Given the power draw increases we’ve seen this generation, those are rather unimpressive results, and actually represent a perf/W regression. AMD’s current 6-core 5600X actually is very near to the new 11700K, but consuming a fraction of the power.

CPU Tests: Encoding and Legacy/Web Gaming Tests: Deus Ex Mankind Divided
Comments Locked

541 Comments

View All Comments

  • dihartnell - Thursday, March 11, 2021 - link

    Traditionally Big.Little designs don't work that way. They either are running the big 8 cores or they are running the little eight cores but not at the same time. The type of workload determines which is run when. Personally don't think it makes a lot of sense In desktop.
  • Jasonovich - Friday, March 12, 2021 - link

    And whats the point of the little chip big chip design, when TMSC will very shortly produce in mass the 5nm and in 2023 the production will move to 3nm.

    Alderlake is based on the worse case scenario and has been introduced to buy Intel time until it resolves the shortfalls of their 10nm production.
  • lmcd - Friday, March 5, 2021 - link

    You're really confused if you think Atom doesn't help Intel here. Tremont performance per watt and performance per die area is really quite excellent. Also worth remembering that nearly every Atom you've ever seen has had mediocre memory and cooling paired with it. I don't expect Intel to "win" off of this move but it'll help for as long as Intel doesn't have chiplet ready.
  • The_Assimilator - Saturday, March 6, 2021 - link

    Even if it does - and Intel's current record on 10nm suggests it won't - by that time AMD will have had over a year of Zen 3 reining unopposed, and Zen 4 well on the way.
  • The_Assimilator - Saturday, March 6, 2021 - link

    *reigning
  • m53 - Friday, March 5, 2021 - link

    291W is for AVX512 workload. The rest of the CPUs here won't match it's performance on AVX512 workloads no matter how much power you give them.

    But if you are not interested in AVX512 workloads then don't look at the AVX512 power consumption.
  • scineram - Saturday, March 6, 2021 - link

    Already beaten in DigiCortex.
  • RaistlinZ - Friday, March 5, 2021 - link

    Ouch. :(
  • terroradagio - Friday, March 5, 2021 - link

    It is incredible bad form and bad taste to release a review before anyone else and before Intel has provided the new microcode update to resolve the early issues. All because Anandtech wants to get out early.

    And your defense by way of saying well we got it at retail and therefore this doesn't matter is a joke. Terrible publication.
  • Makaveli - Friday, March 5, 2021 - link

    lol that power consumption really bothering you ?

Log in

Don't have an account? Sign up now