Section by Andrei Frumusanu

CPU ST Performance: SPEC 2006, SPEC 2017

SPEC2017 and SPEC2006 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. SPEC2006 is deprecated in favor of 2017, but remains an interesting comparison point in our data. 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://

-Ofast -fomit-frame-pointer
-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.

To note, the requirements for the SPEC licence state that any benchmark results from SPEC have to be labelled ‘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.

Starting off with our SPEC2006 analysis for Tiger Lake, given that we’re extremely familiar with the microarchitectural characteristics of these workloads:

SPECint2006 Speed Estimated Scores

As a note, the Tiger Lake figures published in the detailed sub-scores represent the 28W TDP configuration option of the platform, with the core mostly clocking to 4800MHz and all other aspects the device allowing for maximum speed. This allows us for a pure microarchitectural analysis.

The generational improvements of the new Sunny Cove design here is showing very much its advertised characteristics of the microarchitecture.

Starting off with high-IPC and backend execution-bound workloads such as 456.hmmer we’re seeing a near linear performance increase with clock frequency. Sunny Cove here had larger IPC improvements but the Ice Lake design was rather limited in its clock frequency, most of the time still losing out to higher-clocked Skylake designs.

This time around with the major frequency boost, the Tiger Lake chip is able to even outperform the desktop i7-10900K at 5.3GHz as long as memory doesn’t become a bottleneck.

IPC/performance-per-clock wise, things are mostly flat between generation at +-2% depending on workloads, but 473.astar does seem to like the Willow Cove architecture as we’re seeing a +10% boost. 403.gcc’s 4% IPC improvement also likely takes advantage of the larger L2 cache of the design, whilst 429.mcf’s very latency sensitive nature sees a huge 23% IPC boost thanks to the strong memory controllers of Tiger Lake.

462.libquantum doesn’t fare well at all as we’re not only seeing a 30% reduction in IPC, but absolute performance is actually outright worse than Ice Lake. This workload is bandwidth hungry. The theory is that if it has a mostly cache-resident workload footprint, then it would generally make sense to see such a perf degradation due to the L3’s overall degraded generational performance. It’s an interesting aspect we’ll also see in 470.lbm.

SPECfp2006(C/C++) Speed Estimated Scores

In the floating-point workloads, we again see the Tiger Lake chip doing extremely well, but there are some outliers. As mentioned 470.lbm is which is also extremely bandwidth hungry sees a generational degradation, which again could be L3 related, or something more specific to the memory subsystem.

There’s actually a wider IPC degradation in this set, with 482.sphinx being the only positive workload with a +2% boost, while the rest fall in a -12%, -7%, -14%, -3% and that massive -31% degradation for 470.lbm. Essentially, all workload which have stronger memory pressure characteristics.

SPEC2006 Speed Estimated Total

Overall SPEC2006 score performance for Tiger Lake is extremely good. Here we also present the 15W vs 28W configuration figures for the single-threaded workloads, which do see a jump in performance by going to the higher TDP configuration, meaning the design is thermally constrained at 15W even in ST workloads. By the way, this is a core power consumption limitation, as even small memory footprint workloads see a performance jump.

The i7-1185G7 is at the heels of the desktop i9-10900K, trailing only by a few percentage points.

Against the x86 competition, Tiger Lake leaves AMD’s Zen2-based Renoir in the dust when it comes to single-threaded performance. Comparing it against Apple’s A13, things aren’t looking so rosy as the Intel CPU barely outmatches it even though it uses several times more power, which doesn’t bode well for Intel once Apple releases its “Apple Silicon” Macbooks.

Even against Arm’s Cortex-A77 things aren’t looking rosy, as the x86 crowd just all that much ahead considering the Arm design only uses 2W.

SPECint2017 Rate-1 Estimated Scores

Moving onto the newer SPEC2017 suite, we’re seeing a quite similar story across the scaling between the platforms. Tiger Lake and its Willow Cove cores are showcasing outstanding performance as long as things are execution-bound, however do fall behind a bit to the desktop system when memory comes into play. There are two sets of results here, workloads which have high bandwidth or latency requirements, or those which have large memory footprint requirements.

523.xalancbmk_r seems to be of the latter as it’s posting a quite nice 10% IPC jump for Willow Cove while the rest generally in-between -4% regressions or +3-5% improvements.

SPECfp2017 Rate-1 Estimated Scores

In the FP suite, we mostly see again the same kind of characteristics, with performance most of the time scaling in line with the clock frequency of Tiger Lake, with a few outliers here and there in terms of IPC, such as 544.nab_r gaining +9%, or 549.fotonik3d_r regressing by 12%.

Much like in the 2006 suite, the memory bandwidth hungry 519.lbm_r sees a 23% IPC regression, also regressing its absolute performance below that of Ice Lake.

SPEC2017 Rate-1 Estimated Total

Overall, in the 2017 scores, Tiger Lake actually comes in as the leading CPU microarchitecture if you account both the integer and float-point scores together.

Although the design’s absolute performance here is exemplary, I feel a bit disappointed that in general the majority of the performance gains seen today were due to the higher clock frequencies of the new design.

IPC improvements of Willow Cove are quite mixed. In some rare workloads which can fully take advantage of the cache increases we’re seeing 9-10% improvements, but these are more of an exception rather than the rule. In other workloads we saw some quite odd performance regressions, especially in tests with high memory pressure where the design saw ~5-12% regressions. As a geometric mean across all the SPEC workloads and normalised for frequency, Tiger Lake showed 97% of the performance per clock of Ice Lake.

In a competitive landscape where AMD is set to make regular +15% generational IPC improvements and Arm now has an aggressive roadmap with yearly +30% IPC upgrades, Intel’s Willow Cove, although it does deliver great performance, seems to be a rather uninspiring microarchitecture.

Power Consumption: Comparing 15 W TGL to 15 W ICL to 15 W Renoir CPU MT Performance: SPEC 2006, SPEC 2017


View All Comments

  • Rtx dude - Monday, September 28, 2020 - link

    Thank you Reply
  • StingkyMakarel - Friday, September 18, 2020 - link

    anyone tried running multiple single threaded app on Intel and AMD? Reply
  • dsplover - Friday, September 18, 2020 - link

    Yes. A couple actually which each get a Core assignment. I’m an audio geek that came from using a PC for streaming from HDD’s (Seagate 10k SCSI Cheetahs) to a software based synthesizer enthusiast where single core performance is crucial.

    Started with AMD MPs/Tyan Tiger and Coppermine 1GHz CPU’s.

    I’ve concluded that CPU Cache or 4.4GHz on an Intel is optimal.
    Latency from extra cores causes me to adjust audio buffer sizes to compensate which I noticed on the Intel Quads. Conroe Dual Cores were faster for my core locked synths. A larger CPU cache overcame the inefficiencies when i7 Bloomdales hit the market.

    Matisse 3800X was a great chip, but more than the 8 Cores was the same latency issues.

    Looking forward to the Cezanne and maybe a Vermeer as I don’t need killer graphics, 2D is fine. Actually AST ASpeed 2500 Server chips on Supermicro and ASRock workstation/server boards is fine.

    What I seek is the single core performance crown. Intel i7 4790k’s are still in my racks. To make me jump to new builds is a larger cache from Intel. Tiger Lake at 50watts looks great for my needs. 4.4GHz is as good as it gets. But even my ancient i7 5775C using a discrete GFX card, using the 128MB L4 cache for audio (running at 3.3GHz) was on par with the 4GHz 4790k.

    So for me the CPU/IPC gains are appreciated, but cache and CPU running at 4+ GHz are really beneficial.

    Tiger Lake or Cezanne will finally show me the results I need to upgrade.
    Intel and AMD can add all of the Cores they want. Single core performance or larger cache to overcome the latency of additional Cores will mean I can run more high end Filters to shape my sounds with.
  • dromoxen - Saturday, September 19, 2020 - link

    For me these are still too weak GFx despite 2x .. When they can match or better my gtx960 they might have a customer. Otherwise I''ll stick to a downclocked ryzen 4000+gtx960 ..I want low low heat output , and a single APU would be ideal ..ASROCK deskmini styleee . Reply
  • Gondalf - Friday, September 18, 2020 - link

    Not only but the claimed 10/15% IPC boost of Zen 3 will be barely enough to be near with Intel clock to clock. Still Intel process clock clearly better, so the upcoming 8 cores Tiger Lake will be an easy winner over an eight core Zen 3.
    To be noticed, in productive benches Intel core destroy badly Zen. Likely the cache structure is done to perform great on standard laptop SW.
    As usual a core have to be SW optimized, definitively not synthetic benches optimized. More or less the reason Xeon is right now a big winner on Epyc in the 32 cores/cpu market (the larger).
  • Spunjji - Friday, September 18, 2020 - link

    You say this every time a new AMD processor is due, and every time you're wrong, and the next time you say the same damned things again. 😑 Reply
  • close - Friday, September 18, 2020 - link

    Subjective opinion time. Ian & Andrei, leaving aside individual scores (great ST performance for Intel, great MT performance for AMD), which one would you buy for day to day "regular" work?

    I've read opinions like "I made it painfully clear that the top-of-the-line Intel CPU at its highest cTDP was only going up against a mid-grade Ryzen" and there's still room for personal opinion here. Should you have to buy one now "money no issue" and ignoring specialized fields (like AI stuff where AVX-512 makes sense) which would you put your money on?
  • Spunjji - Friday, September 18, 2020 - link

    I look forwards to the day when this Intel shill troll gets banned. Reply
  • melgross - Sunday, September 20, 2020 - link

    Oh, come on. We have both AMD and Intel trolls here. They cancel out. Reply
  • Spunjji - Sunday, September 20, 2020 - link

    There's being a fanboy, then there's creating an entire alter ego as some desperate attempt at satire that is inherently self-satirizing of the person running the account. I find this one deeply tiresome. Reply

Log in

Don't have an account? Sign up now