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 i3-7350K, by virtue of its higher frequency, seems to require a good voltage to get up to speed. This is more than enough to go above and beyond the Core i5, which despite having more cores, is in the nicer part (efficiency wise) in the voltage/frequency curve. As is perhaps to be expected, the Core i7-2600K uses more power, having four cores with hyperthreading and a much higher TDP.

Overclocking

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.

For our testing, we overclocking all cores under all conditions:

The overclocking experience with the Core i3-7350K matched that from our other overclockable processors - around 4.8-5.0 GHz. The stock voltage was particularly high, given that we saw 1.100 volts being fine at 4.2 GHz. But at the higher frequencies, depending on the quality of the CPU, it becomes a lot tougher maintain a stable system. With the Core i3, temperature wasn't really a feature here with our cooler, and even hitting 4.8 GHz was not much of a strain on the power consumption either - only +12W over stock. The critical thing here is voltage and stability, and it would seem that these chips would rather hit the voltage limit first (and our 1.4 V limit is really a bit much for a 24/7 daily system anyway). 

A quick browse online shows a wide array of Core i3-7350K results, from 4.7 GHz to 5.1 GHz. Kaby Lake, much like previous generations, is all about the luck of the draw - if you want to push it to the absolute limit.

Gaming: Shadow of Mordor Core i3-7350K vs Core i7-2600K: More MHz Cap'n!
Comments Locked

186 Comments

View All Comments

  • watzupken - Friday, February 3, 2017 - link

    A dual core processor is still a dual core processor even if it is unlocked and offers a high clockspeed. I still feel Kaby Lake is a lazy upgrade over Skylake considering it barely offers anything new. Just take a look at the feature page to get a sense of the "upgrades". With competition coming from ARM and AMD Ryzen, is Intel only capable of a clockspeed war just like they did for Pentium 4?
  • CaedenV - Friday, February 3, 2017 - link

    Well, to be fair Kabby Lake isn't for you and I. It is Skylake with very minor improvements mostly aimed at fixing the firmware level sleep and wake issues that manufacturers had (ie, the reason Apple didn't move to Skylake until well after release, and the botched deployment of the Surface Pro 4).
    Outside of that it is just skylake with a minor clock bumb, slightly better thermals, and more of the chip on 14nm.
  • Shadowmaster625 - Friday, February 3, 2017 - link

    So it will be 2025 before an i3 beats a stock 2600K in all benchmarks? That must mean it will be 2030 before it can beat a 4.8GHz 2600K. That's crazy, considering how badly the Core2Quad compares to even a modern celeron.
  • user_5447 - Friday, February 3, 2017 - link

    Page 2: "There is one caveat however – Speed Shift currently only works in Windows 10. It requires a driver which is automatically in the OS (v2 doesn’t need a new driver, it’s more a hardware update), but this limitation does mean that Linux and macOS do not benefit from it."

    This is incorrect: support for Speed Shift (HW pstates) was commited to Linux kernel back in November of 2014, way before Skylake release.
    https://lkml.org/lkml/2014/11/6/628
  • Hinton - Friday, February 3, 2017 - link

    Of the 3 CPU'S Anandtech received to review, this was the only one that was marginally interesting (we didn't need a review to know Kabylake performs equally to Skylake).

    So of course you spent one month before reviewing it. Good for Anand that he took the money and ran.
  • fanofanand - Friday, February 3, 2017 - link

    You may be unaware, but Ian has been kind of busy lately......
  • Meteor2 - Sunday, February 5, 2017 - link

    He has? How so?
  • PCHardwareDude - Friday, February 3, 2017 - link

    This would be interesting if the part wasn't so bloody expensive. $120 would be interesting.
    At this price, you're better off spending a little more and getting an i5 or spending a lot less and getting the G4600, which is also dual core kaby lake with hyperthreading.
  • AssBall - Friday, February 17, 2017 - link

    If you have a GPU
  • notjamie - Friday, February 3, 2017 - link

    At £170 this is the exact price I paid for my 3570k almost 5 years ago. That's what I call progress.

Log in

Don't have an account? Sign up now