Power Consumption

As with all the major processor launches in the past few years, performance is nothing without a good efficiency to go with it. Doing more work for less power is a design mantra across all semiconductor firms, and teaching silicon designers to build for power has been a tough job (they all want performance first, naturally). Of course there might be other tradeoffs, such as design complexity or die area, but no-one ever said designing a CPU through to silicon was easy. Most semiconductor companies that ship processors do so with a Thermal Design Power, which has caused some arguments recently based presentations broadcast about upcoming hardware.

Yes, technically the TDP rating is not the power draw. It’s a number given by the manufacturer to the OEM/system designer to ensure that the appropriate thermal cooling mechanism is employed: if you have a 65W TDP piece of silicon, the thermal solution must support at least 65W without going into heat soak.  Both Intel and AMD also have different ways of rating TDP, either as a function of peak output running all the instructions at once, or as an indication of a ‘real-world peak’ rather than a power virus. This is a contentious issue, especially when I’m going to say that while TDP isn’t power, it’s still a pretty good metric of what you should expect to see in terms of power draw in prosumer style scenarios.

So for our power analysis, we do the following: in a system using one reasonable sized memory stick per channel at JEDEC specifications, a good cooler with a single fan, and a GTX 770 installed, we look at the long idle in-Windows power draw, and a mixed AVX power draw given by OCCT (a tool used for stability testing). The difference between the two, with a good power supply that is nice and efficient in the intended range (85%+ from 50W and up), we get a good qualitative comparison between processors. I say qualitative as these numbers aren’t absolute, as these are at-wall VA numbers based on power you are charged for, rather than consumption. I am working with our PSU reviewer, E.Fylladikatis, in order to find the best way to do the latter, especially when working at scale.

Nonetheless, here are our recent results for Kaby Lake at stock frequencies:

Power Delta (Long Idle to OCCT)

The Core i5-7600K, despite the 91W TDP rating, only achieved 63W in our power test. This is relatively interesting, suggesting that the Core i5 sits in a good power bracket for voltage (we see that with overclocking below), but also the mixed-AVX loading only starts piling on the power consumption when there are two hyperthreads going for those instructions at the same time per core. When there’s only one thread per core for AVX, there seems to be enough time for each of the AVX units to slow down and speed back up, reducing overall power consumption.


At this point I’ll assume that as an AnandTech reader, you are au fait with the core concepts of overclocking, the reason why people do it, and potentially how to do it yourself. The core enthusiast community always loves something for nothing, so Intel has put its high-end SKUs up as unlocked for people to play with. As a result, we still see a lot of users running a Sandy Bridge i7-2600K heavily overclocked for a daily system, as the performance they get from it is still highly competitive.

There’s also a new feature worth mentioning before we get into the meat: AVX Offset. We go into this more in our bigger overclocking piece, but the crux is that AVX instructions are power hungry and hurt stability when overclocked. The new Kaby Lake processors come with BIOS options to implement an offset for these instructions in the form of a negative multiplier. As a result, a user can stick on a high main overclock with a reduced AVX frequency for when the odd instruction comes along that would have previously caused the system to crash.

We used the AVX Offset option when we overclocking the Core i7-7700K and achieved another 100-200 MHz extra frequency for non-AVX before succumbing to overheating. Ultimately that’s not a lot of frequency, but that can be enough for some users. With the Core i5-7600K, we got a great result without even touching the AVX offset option:

Straight out of the box, our retail sample achieved an OCCT stable 5.0 GHz with mixed AVX at a 1.375V setting, with the software recording only 58C peak on the core and a maximum power draw of 111W. That’s fairly astonishing – from the base 3.8/4.2 GHz we were able to get up to 800 MHz in an overclock for just under double the power draw (or, +20W over TDP).

Gaming: Shadow of Mordor Conclusion: The Cooler and Cheaper Choice


View All Comments

  • Gastec - Wednesday, January 11, 2017 - link

    I remember that when Windows XP came out, more than 15 years ago, eveybody was crying out loud (some hysterically) that Windows 98 is waaay better and they will never upgrade to XP.
    But enough about operating systems, that discussion is irrelevant. I'm more interested in learning about the things (voices?) that YOU HEAR and record :)
  • serpretetsky - Tuesday, January 3, 2017 - link

    Maybe I went over the article too fast, is there something specific about this chip to windows 10? Reply
  • nico_mach - Tuesday, January 3, 2017 - link

    Speedstep is unique to Windows 10. Reply
  • Bullwinkle J Moose - Tuesday, January 3, 2017 - link

    probably not but do any of the motherboards support IDE ?

    Does the chip itself have XP drivers?

    Probably not

    Waste of money
  • Murloc - Tuesday, January 3, 2017 - link

    if you don't like windows you can use linux.

    With XP you're not getting the most recent versions of directx anyway so you're probably not gaming on it, so what's the reason for sticking to windows?
  • doggface - Wednesday, January 4, 2017 - link

    Seriously... Wow. Troll much. Reply
  • Bullwinkle J Moose - Wednesday, January 4, 2017 - link

    never Reply
  • Shadow7037932 - Wednesday, January 4, 2017 - link

    Loss of $500-1K from you is not a big deal for Intel or any other OEM. Reply
  • Outlander_04 - Tuesday, January 3, 2017 - link

    Looks like intel are worried about Zen enough they have bumped up stock clocks .
    They have achieved that with out too much extra power consumption which is something I guess , but kaby lake is not a step forward
  • Murloc - Tuesday, January 3, 2017 - link

    optimization is just that, why would we expect something more? Reply

Log in

Don't have an account? Sign up now