Power Consumption: Hot Hot HOT

I won’t rehash the full ongoing issue with how companies report power vs TDP in this review – we’ve covered it a number of times before. But in a quick sentence, Intel uses one published value for sustained performance, and an unpublished ‘recommended’ value for turbo performance, the latter of which is routinely ignored by motherboard manufacturers. Most high-end consumer motherboards ignore the sustained value, often 125 W, and allow the CPU to consume as much as it needs with the real limits being the full power consumption at full turbo, the thermals, or the power delivery limitations.

One of the dimensions of this we don’t often talk about is that the power consumption of a processor is always dependent on the actual instructions running through the core.  A core can be ‘100%’ active while sitting around waiting for data from memory or doing simple addition, however a core has multiple ways to run instructions in parallel, with the most complex instructions consuming the most power. This was noticeable in the desktop consumer space when Intel introduced vector extensions, AVX, to its processor design. The concurrent introduction of AVX2, and AVX-512, means that running these instructions draws the most power.

AVX-512 comes with its own discussion, because even going into an ‘AVX-512’ mode causes additional issues. Intel’s introduction of AVX-512 on its server processors showcased that in order to remain stable, the core had to reduce the frequency and increase the voltage while also pausing the core to enter the special AVX-512 power mode. This made the advantage of AVX-512 suitable only for strong high-performance server code. But now Intel has enabled AVX-512 across its product line, from notebook to enterprise, allowing these chips to run AI code faster and enabling a new use cases. We’re also a couple of generations on from then, and AVX-512 doesn’t get quite the same hit as it did, but it still requires a lot of power.

For our power benchmarks, we’ve taken several tests that represent a real-world compute workload, a strong AVX2 workload, and a strong AVX-512 workload. Note that Intel lists the Core i7-11700K as a 125 W processor.

Motherboard 1: Microcode 0x2C

Our first test using Agisoft Photoscan 1.3 shows a peak power consumption around 180 W, although depending on the part of the test, we have sustained periods at 155 W and 130 W. Peak temperatures flutter with 70ºC, but it spends most of the time at around the 60ºC mark.

For the AVX2 workload, we enable POV-Ray. This is the workload on which we saw the previous generation 10-core processors exceed 260 W.

At idle, the CPU is consuming under 20 W while touching 30ºC. When the workload kicks in after 200 seconds or so, the power consumption rises very quickly to the 200-225 W band. This motherboard implements the ‘infinite turbo’ strategy, and so we get a sustained 200-225 W for over 10 minutes. Through this time, our CPU peaks at 81ºC, which is fairly reasonable for some of the best air cooling on the market. During this test, a sustained 4.6 GHz was on all cores.

Our AVX-512 workload is 3DPM. This is a custom in-house test, accelerated to AVX2 and AVX512 by an ex-Intel HPC guru several years ago (for disclosure, AMD has a copy of the code, but hasn’t suggested any changes).

This tests for 10-15 seconds and then idles for 10 seconds, and does rapidly go through any system that doesn’t run an infinite turbo. What we see here in this power only graph is the alarming peaks of 290-292 W. Looking at our data, the all-core turbo under AVX-512 is 4.6 GHz, sometimes dipping to 4.5 GHz. Ouch. But that’s not all.

Our temperature graph looks quite drastic. Within a second of running AVX-512 code, we are in the high 90ºC, or in some cases, 100ºC. Our temperatures peak at 104ºC, and here’s where we get into a discussion about thermal hotspots.

There are a number of ways to report CPU temperature. We can either take the instantaneous value of a singular spot of the silicon while it’s currently going through a high-current density event, like compute, or we can consider the CPU as a whole with all of its thermal sensors. While the overall CPU might accept operating temperatures of 105ºC, individual elements of the core might actually reach 125ºC instantaneously. So what is the correct value, and what is safe?

The cooler we’re using on this test is arguably the best air cooling on the market – a 1.8 kilogram full copper ThermalRight Ultra Extreme, paired with a 170 CFM high static pressure fan from Silverstone. This cooler has been used for Intel’s 10-core and 18-core high-end desktop variants over the years, even the ones with AVX-512, and not skipped a beat. Because we’re seeing 104ºC here, are we failing in some way?

Another issue we’re coming across with new processor technology is the ability to effectively cool a processor. I’m not talking about cooling the processor as a whole, but more for those hot spots of intense current density. We are going to get to a point where can’t remove the thermal energy fast enough, or with this design, we might be there already.

Smaller Packaging

I will point out an interesting fact down this line of thinking though, which might go un-noticed by the rest of the press – Intel has reduced the total vertical height of the new Rocket Lake processors.

The z-height, or total vertical height, of the previous Comet Lake generation was 4.48-4.54 mm. This number was taken from a range of 7 CPUs I had to hand. However, this Rocket Lake processor is over 0.1 mm thinner, at 4.36 mm. The smaller height of the package plus heatspreader could be a small indicator to the required thermal performance, especially if the airgap (filled with solder) between the die and the heatspreader is smaller. If it aids cooling and doesn’t disturb how coolers fit, then great, however at some point in the future we might have to consider different, better, or more efficient ways to remove these thermal hotspots.

Motherboard 2: Microcode 0x34

As an addendum to this review a week after our original numbers, we obtained a second motherboard that offered a newer microcode version from Intel.

On this motherboard, the AVX-512 response was different enough to warrant mentioning. Rather than enable a 4.6 GHz all-core turbo for AVX-512, it initially ramped up that high, peaking at 276 W, before reducing down to 4.4 GHz all-core, down to 225 W. This is quite a substantial change in behaviour:

This means that at 4.4 GHz, we are running 200 MHz slower (which gives a 3% performance decrease), but we are saving 60-70 W. This is indicative of how far away from the peak efficiency point that these processors are.

There was hope that this will adjust the temperature curve a little. Unfortunately we still see peaks at 103ºC when AVX-512 is first initiated, however during the 4.4 GHz time scale we are more akin to 90ºC, which is far more palatable.

On AVX2 workloads with the new 0x34 microcode, the results were very similar to the 0x2C microcode. The workload ran at 4.6 GHz all-core, reached a peak power of 214 W, and the processor temperature was sustained around 82ºC.

Peak Power Comparison

For completeness, here is our peak power consumption graph. These are the peak power consumption numbers taken from a series of benchmarks on which we run our power monitoring tools.

(0-0) Peak Power

Intel Core i7-11700K Review CPU Tests: Microbenchmarks
Comments Locked

541 Comments

View All Comments

  • GeoffreyA - Tuesday, March 9, 2021 - link

    Cage of their own making: I like that phrase. Well, I think for Intel, the best path is to design a microarchitecture from scratch, which I'm sure they're doing. Possibly Intel Israel. Sunny Cove, descending all the way from P6, is not holding up any more.
  • Zim - Sunday, March 7, 2021 - link

    Time to be me some more AMD stock.
  • alhopper - Sunday, March 7, 2021 - link

    What an awesome deep-dive technical expose/review of this processor. No stone left un-turned - incredibly detailed investigation and easily understood explanations. With this level of detail every reader can make up their own mind about the pros/cons of this product - there's no need for me to offer an opinion.
    Many thanks for this well written treasure trove of technical information and the graphics are wonderful. Kudos to the entire team and keep up the Good Work (TM) !!
  • poohbear - Sunday, March 7, 2021 - link

    Wow how the tables have turned. I remember for AMD's Bulldozer review, which was supposed to be AMD's answer to Core, Bulldozer was similar to Rocket Lake...it consumed MORE power and was SLOWER than the competition. Well, here's to Intel making a comeback with Alder Lake, but 2021 clearly belongs to AMD.
  • Hifihedgehog - Monday, March 8, 2021 - link

    Alder Lake, just confirmed in a lineup leak to use a heavy amount of little or low power cores, first has to ensure that they get heterogenous core architecture working in the Windows scheduler. The biggest roadblock Microsoft claimed to have already fixed it with Lakefield but even after they did and additionally Cinebench, per Intel’s special emergency request, to recompile a special update to R20 after that, Lakefield was an absolute failure in performance compared to a Y-class (or M notated) Core product. Personally, I have little faith in Microsoft and I also do not expect software companies recompiling every last piece of software made in the last decade either just to accommodate a radical new design all for Intel’s sake. Developers would much rather assume a simple, vanilla core architecture than an unbalanced one with little and big cores and therein lies a huge risk factor for Intel. I foresee a huge misfire here because Microsoft isn’t exactly a good company to bet on refixing what they claimed they have already fixed with Lakefield.
  • GeoffreyA - Monday, March 8, 2021 - link

    I'm sceptical of this whole fast/slow core approach myself and believe it's a mistake. They will learn the hard way. Perhaps it works for Apple, I don't know, but Intel and AMD are better of spending their efforts in cutting down power in their ordinary cores dynamically.
  • Hifihedgehog - Monday, March 8, 2021 - link

    It works for Apple because they have a iron-tight grasp on the full stack which requires developers to use their latest compilation and development tools to get their apps to the App Store and ultimately in users’ hands. You can run pretty much anything under the sun for 2 decades plus on Windows and without a recompile, you will never utilize their cores correctly. The Windows scheduler as it stands is garbage tier compared to Linux with a plain vanilla homogenous core design so I expect very little from Microsoft unless they actually redesign their scheduler from the ground up. Don’t hold your breath on that one.
  • GeoffreyA - Monday, March 8, 2021 - link

    The whole idea smacks of Bulldozer, and that means disaster.
  • blppt - Monday, March 8, 2021 - link

    Only if their single thread performance sucks (which from all I've seen, it won't)---Bulldozer's problem was being behind in manufacturing process and requiring a highly-threaded application to shine.
  • Hifihedgehog - Tuesday, March 9, 2021 - link

    Well, the problem then is how smartly it assigns threads to the right cores and the Windows scheduler still has serious problems with that to this very day. If it doesn’t do that right, it could appear like an overclocked Core i3 in comparison to Ryzen and that is where the Bulldozer analogy is fitting. AMD banked on their unique topology getting OS and development optimization down the road—FineWine to coin a phrase—but that never materialized.

Log in

Don't have an account? Sign up now