SPEC2017 Single-Threaded Results

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 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 it is good enough. Because our scores aren’t official submissions, as per SPEC guidelines we have to declare them as internal estimates on 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-source 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.

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.

SPECint2017 Rate-1 Estimated Scores

Opening things up with SPECint2017 single-threaded performance, it's clear that Intel has improved ST performance for Raptor Lake on generation-upon-generation basis. Because the Raptor Cove P-cores used here don't deliver significant IPC gains, these performance gains are primarily being driven by the chip's higher frequency. In particular, Intel has made notable progress in improving their v/f curve, which allows Intel to squeeze out more raw frequency.

And this is something Intel's own data backs up, with one of Intel's performance breakdown slides showing that the bulk of the gains are due to frequency, while improved memory speeds and the larger caches only making small contributions.

The ST performance itself in SPECint2017 is marginally better going from Alder Lake to Raptor Lake, but these differences can certainly be explained by the improvements as highlighted above. What's interesting is the performance gap between the Core i9-13900K and the Ryzen 9 7950X isn't as far apart as it was with Alder Lake vs. Ryzen 9 5950X. In 500.perlbench_r, the Raptor Lake chip actually outperforms the Zen 4 variant by just under 4%, while Ryzen 9 7950X is a smidgen over 10% better in the 505.mcf_r test. 

SPECfp2017 Rate-1 Estimated Scores

Looking at the second set of SPEC2017 results (fp), the Ryzen 9 7950X is ahead of the Core i9-13900K by 16% in the 503.bwaves_r test, while the Raptor Lake chip is just under 10% better off in the 508.namd_r test. The key points to digest here is that Intel has done well to bridge the gap in single-threaded performance to Ryzen 7000 in most of the tests, and overall, it's a consistent trade-off between which test favors which mixture of architecture, frequency, and most importantly of all, IPC performance.

While we highlighted in our AMD Ryzen 9 7950X processor review, which at the time of publishing was the clear leader in single-core performance, it seems as though Intel's Raptor Lake is biting at the heels of the new Zen 4-core. In some instances, it's actually ahead, but stiff competition from elsewhere is always good as competition creates innovation.

With Raptor Lake being more of a transitional and enhanced core design that Intel's worked with before (Alder Lake), it remains to be seen what the future of 2023 holds for Intel's advancement in IPC and single-threaded performance. Right now, however SPEC paints a picture where it's pretty much neck and neck between Raptor Cove and Zen 4.

Core-to-Core Latency SPEC2017 Multi-Threaded Results
POST A COMMENT

169 Comments

View All Comments

  • Pjotr - Thursday, October 20, 2022 - link

    Closing thoughts typos: Ryzen 580X3D and Ryzen 700. Reply
  • Ryan Smith - Thursday, October 20, 2022 - link

    Thanks! Reply
  • mode_13h - Thursday, October 20, 2022 - link

    Thanks for the review!

    Could you please add the aggregates, in the SPEC 2017 scores? There's usually a summary chart that has an average of the individual benchmarks, and then it often has the equivalent scores from more CPUs/configurations than the individual test graphs contain. For example, see the Alder Lake review:

    https://www.anandtech.com/show/17047/the-intel-12t...
    Reply
  • Arbie - Thursday, October 20, 2022 - link

    TechSpot / Hardware Unboxed show that to complete a Blender job the 13900K takes 50% more total system energy than does the 7950X. Intel completing a Cinebench job takes 70% more energy. Meaning heat in the room. And that's with the Intel chip thermal throttling instantly on even the best cooling.

    Looking at AT's "Power" charts here, which list the Intel chip as "125W" and AMD as "170W", many readers will get EXACTLY THE OPPOSITE impression.

    Sure, you mention the difficulties in comparing TDPs etc, and compare this gen Intel to last gen etc but none of that "un-obscures" the totally erroneous Intel vs AMD picture you've conveyed.

    ESPECIALLY when your conclusion says they're "very close in performance" !! BAD JOB, AT. The worst I've seen here in a very long time. Incomprehensibly bad.
    Reply
  • gezafisch - Thursday, October 20, 2022 - link

    Cope harder - watch Der8auer's video showing that the 13900k can beat any chip at efficiency with the right settings - https://youtu.be/H4Bm0Wr6OEQ Reply
  • Ryan Smith - Thursday, October 20, 2022 - link

    We go into the subject of power consumption at multiple points and with multiple graphs, including outlining the 13900K's high peak power consumption in the conclusion.

    https://images.anandtech.com/graphs/graph17601/130...

    Otherwise, the only place you see 125W and 170W are in the specification tables. And those values are the official specifications for those chips.
    Reply
  • boeush - Thursday, October 20, 2022 - link

    Not true. You have those insanely misleading "TDP" labels on every CPU in the legend of every performance comparison chart. This paints a very misleading picture of "competitive" performance, whereas performance at iso-power (e.g. normalized per watt, based on total system power consumption measured at the outlet) would be much more enlightening. Reply
  • boeush - Thursday, October 20, 2022 - link

    *per watt-hour (not per watt)

    [summed over the duration of the benchmark run]
    Reply
  • dgingeri - Thursday, October 20, 2022 - link

    Is it just me, or does the L1 cache arrangement seem a bit odd? 48k data and 32k instruction for the P cores and 32k data and 64k instruction on the e-cores. Seems a bit odd to me. Reply
  • Otritus - Thursday, October 20, 2022 - link

    Golden/Raptor Cove has a micro-op cache for instructions. 4096 micro-ops is about equal to 16Kb of instruction cache, which is effectively 48Kb-D + 48Kb-I. I don’t remember whether Gracemont has a micro-op cache. However, it doesn’t have hyperthreading, so maybe it just needs less data cache per core. Reply

Log in

Don't have an account? Sign up now