Power Consumption

With the two Kaby Lake-X processors, the main comparison for power consumption is going to be against their Kaby Lake-S counterparts on the mainstream platform. For an extra 100 MHz, Intel is moving from a 95W TDP to a 112W TDP, indicating that these processors will need better cooling – but when we tested KBL-S we were rather surprised by the power, especially on the Core i5.

Power: Total Package (1T)

Power: Total Package (Full Load)

The Core i5-7640X almost perfectly matches up with its Core i5 counterparts, even beating the Core i5-7600K in every situation but especially at load. For users who want to overclock near to the official TDP, it looks like there’s some headroom (other circumstances permitting). The Core i7-7740X is noticeably more power hungry at full load, hitting 79W, but lower than the Core i7-7700K at 87W.

Overclocking to 5.0 GHz

One of the elements promoted at the launch of Basin Falls was overclockability: Intel ran a private invite-only extreme overclocking workshop with sub-zero coolants that week, which was then followed by ASUS and GIGABYTE both stepping it up another gear by using liquid helium rather than liquid nitrogen. For some of these chips, the colder the better, and liquid helium is going to be limit for cooling (and cost) as there is inherent difficulty in using sub-zero coolants for records.

Those sub-zero events for records are just on single benchmarks, or single frequency records, and are not meant to be run at those speeds all day every day. This makes the air and water overclocking potential of the CPUs more important for regular users and enthusiasts.

When Kaby Lake-S was launched, we saw good overclocking performance on the Core i7-7700K: our set of 4.2 GHz base processors reached a range between 4.6 to 4.8 GHz, arguably giving a 8-15% overclock and given some of the numbers we had seen in the wild, the consistency between the processors meant that most of the 7700K CPUs could reach that amount. One of the reasons for such good performance on these CPUs was that Intel had incorporated a new feature for overclocking, the AVX offset. This allows overclockers to reduce the frequency that AVX code runs at, as this can be a limiting factor when it comes to a stable overclock. This feature is in Kaby Lake-X as well.

The end result is that the Core i7-7740X went one further in our testing, and hit 5.0 GHz all-cores at 1.25V, and completed our CPU testing suite with a -10 AVX offset. We went for 5.1 GHz all-core, up to 1.35 volts, but the temperatures were getting high and the system was still not stable. 5.0 GHz is a very respectable result, even if we only have a sample of one.

The results at 5.0 GHz are as follows. Gain is absolute for the benchmark for the 5.0 GHz value, with anything within 2.0% listed in orange. Green indicates a win for the faster chip.

Comparison: Intel Core i7-7740X at Stock vs 5 GHz
4.3 GHz Base
4.5 GHz Turbo
Auto AVX
  5.0 GHz Base
5.0 GHz Turbo
4.0 GHz AVX
Score / Time Web Benchmarks Score / Time Gain
135 ms Sunspider 133 ms +1.6%
622 ms Kraken 642 ms -3.1%
45485 Octane 45279 -0.5%
561 WebXPRT15 570 +1.5%
  System Tests    
2229 ms PDF Opening 2055 ms +8.5%
46.172 s FCAT 45.656 s +1.1%
1287 3DPM 2.1 1429 +11.0%
282 s Dolphin v5 280 s +0.7%
891.56 s Agisoft Total 830.06 s +7.4%
  Rendering    
2474593 Corona 2660002 +7.5%
436 s Blender 485 s -10.1%
195 Cinebench 15 ST 215 +10.6%
986 Cinebench 15 MT 1084 +10.0%
  Encoding    
27433 7-zip 29433 +8.9%
48.698 s WinRAR 46.633 s +4.4%
5.5 GB/s AES 6.2 GB/s +12.7%
25.2 FPS Handbrake HEVC 22.6 FPS -10.2%
  Office Tests    
4878 PCMark8 Creative 5084 +4.2%
4844 PCMark8 Home 5071 +4.7%
4110 PCMark8 Work 3984 +3.2%
19.45 per day Chrome Compile 17.70 per day -9.0%
  GTX 1080    
72.56 FPS 1080p Ashes Av 76.19 FPS +4.8%
53.95 FPS 1080p Ashes 99% 55.45 FPS +2.7%
62.30 FPS 4K Ashes Av 63.46 FPS +1.8%
41.24 FPS 4K Ashes 99% 40.79 FPS -1.1%
103.66 FPS 1080p RoTR-1 Av 106.9 FPS +3.0%
85.14 FPS 1080p RoTR-1 99% 85.88 FPS +0.9%
61.60 FPS 4K RoTR-1 Av 61.33 FPS -0.4%
50.25 FPS 4K RoTR-1 99% 50.43 FPS +0.3%

There are a few obvious trends, and a couple of red flags. Most benchmarks split themselves into two groups: benchmarks with a heavy CPU component tend to get a 4-12% gain when overclocked, and those that require a lot of DRAM involvement or AVX tend to be in the 2% region. The red flags are the three big 9-10% loss values for CPU heavy benchmarks, Blender, Handbrake HEVC and Chrome Compilation.

All three benchmarks are sizable workloads with sustained high frequencies throughout, and have heavy AVX components as well. The 4.0 GHz setting for AVX could account for most of that difference, however other AVX benchmarks in our testing (Corona, Cinebench, elements of PCMark, Agisoft) do not have the same effect. The only real difference here is time: the amount of time each benchmark stays at a sustained load.

The three that had the biggest dips are our longest benchmarks: Blender at 8 minutes, Handbrake HEVC at 25 minutes, and the Chrome Compile at over an hour. In this case it seems we are hitting thermal limits for the power delivery, as explained by Igor Wallossek over at Tom's Hardware. He tested an upcoming theory that the early X299 boards are not up to the task for cooling VRMs at heavy load, and through analysis he determined that this was likely to occur in heavily overclocked scenarios. His data showed that the Skylake systems he tested, when overclocked, would hit thermal limits, come back down, and then ramp up again in a cyclical manner. He tested Skylake-X, which draws a lot more power overclocked than our KBL-X setup here, so it likely isn't affecting our setup as much, but still enough for certain benchmarks. I fully suspect we will see second-wave X299 motherboards with substantial heatsinks on the power delivery to overcome this.

More testing is needed, especially in upcoming X299 motherboard reviews. We used an early X299 prototype for our CPU testing here, and a Gaming 9 motherboard on the GPU tests (which showed little variation and no problems). We did take power numbers for this setup but when looking back on the results, they seemed off so we need to go back and re-test those.

Gaming Performance: Grand Theft Auto (1080p, 4K) Conclusion: The Fastest for Serial Workloads
Comments Locked

176 Comments

View All Comments

  • djayjp - Monday, July 24, 2017 - link

    Ian, why didn't you check if the OC was being thermally throttled? Easy enough to check this. And easy enough to see if it's the temperature of the cores or not. Surprising you wouldn't include temperature or power consumption data with the OC (though I understand this hasn't typically been a focus of AT). Another site demonstrated throttling at ~95+ C.
  • mapesdhs - Monday, July 24, 2017 - link

    Is that the same site which showed that the TIM Intel is using is just not allowing the heat to get from the die to the cap? Die temp shoots up, cap temp doesn't, even with a chiller cooler.
  • melgross - Monday, July 24, 2017 - link

    This article gives a good reason why huge numbers of core are a waste of money for most users.

    http://www.computerworld.com/article/3209724/compu...
  • Old_Fogie_Late_Bloomer - Monday, July 24, 2017 - link

    Yeah, don't bother starting the article unless you're willing to create yet another useless online identity. Shame, since it seemed moderately interesting, but...
  • alpha754293 - Monday, July 24, 2017 - link

    re: overclocking
    That works well for the occasional heavy workload, but if you are going to be constantly running at peak load (like I did for engineering analysis), overclocking of any kind, from my experience, isn't worth the dead core or entire CPU.

    I've already fried a core on the 3930K once before taking it up from 3.2 GHz stock, 3.5 GHz max TurboBoost to 4.5 GHz.
  • mapesdhs - Monday, July 24, 2017 - link

    Alas this stuff does vary according to the invidual CPU, mbd, RAM, etc. What cooling did you use? Could also be the vcore was too high - a lot of SB-E users employed a high vcore, not realising that using a lower PLL would often make such a high vcore unnecessary. It's even more complicated if one fills all 8 RAM slots on a typical X79 mbd.
  • alpha754293 - Tuesday, July 25, 2017 - link

    The cooling that I was using was Corsair H80i v2.

    The temps were fine and were consistently fine.

    RAM was 8x 8 GB Cruical Ballistix Sport I think DDR3-1600? Something like that. Nothing special, but nothing super crappy either. I actually had the entire set of RAM (all eight DIMMs RMA'd once) so I know that I got a whole new set back when that happened about oh...maybe a-year-and-a-half ago now? Something like that.

    Motherboard was Asus X79 Sabertooth.

    Yeah, I had all 8 DIMM slots populated because it was a cheaper option compared to 4x 16 GB. Besides, using all 8 DIMMs also was able to make use of the quad-channel memory whereas going with 4x 16 GB - you can't/won't (since the memory needed to be installed in paired DIMM slots).

    That CPU is now "castrated" down to 4 cores (out of 6) because 1 of the cores died (e.g. will consistently throw BSODs, but if I disable it, no problems). Makes for a decent job scheduler (or at least that's the proposed task/life for it).
  • Dr. Swag - Monday, July 24, 2017 - link

    Hey Ian, on the first page you listed the turbo of the 7700k as 4.4, whereas it's actually 4.5
  • Yuriman - Monday, July 24, 2017 - link

    Shouldn't the 7700K read "4.2-4.5ghz" rather than 4.2-4.4?
  • Dug - Monday, July 24, 2017 - link

    On RoTR-1-Valley 1080p it shows i5 7600k at 141fps and the i7 7700k at 103fps. Have a feeling these might be transposed.

Log in

Don't have an account? Sign up now