Overclocking

For our final evaluation of the GTX 1080 and GTX 1070 Founders Edition cards, let’s take a look a overclocking.

Whenever I review an NVIDIA reference card, I feel it’s important to point out that while NVIDIA supports overclocking – why else would they include fine-grained controls like GPU Boost 3.0 – they have taken a hard stance against true overvolting. Overvolting is limited to NVIDIA’s built in overvoltage function, which isn’t so much a voltage control as it is the ability to unlock 1-2 more boost bins and their associated voltages. Meanwhile TDP controls are limited to whatever value NVIDIA believes is safe for that model card, which can vary depending on its GPU and its power delivery design.

For GTX 1080FE and its 5+1 power design, we have a 120% TDP limit, which translates to an absolute maximum TDP of 216W. As for GTX 1070FE and its 4+1 design, this is reduced to a 112% TDP limit, or 168W. Both cards can be “overvolted” to 1.093v, which represents 1 boost bin. As such the maximum clockspeed with NVIDIA’s stock programming is 1911MHz.

GeForce GTX 1080FE Overclocking
  Stock Overclocked
Core Clock 1607MHz 1807MHz
Boost Clock 1734MHz 1934MHz
Max Boost Clock 1898MHz 2088MHz
Memory Clock 10Gbps 11Gbps
Max Voltage 1.062v 1.093v

 

GeForce GTX 1070FE Overclocking
  Stock Overclocked
Core Clock 1506MHz 1681MHz
Boost Clock 1683MHz 1858MHz
Max Boost Clock 1898MHz 2062MHz
Memory Clock 8Gbps 8.8Gbps
Max Voltage 1.062v 1.093v

Both cards ended up overclocking by similar amounts. We were able to take the GTX 1080FE another 200MHz (+12% boost) on the GPU, and another 1Gbps (+10%) on the memory clock. The GTX 1070 could be pushed another 175MHz (+10% boost) on the GPU, while memory could go another 800Mbps (+10%) to 8.8Gbps.

Both of these are respectable overclocks, but compared to Maxwell 2 where our reference cards could do 20-25%, these aren’t nearly as extreme. Given NVIDIA’s comments on the 16nm FinFET voltage/frequency curve being steeper than 28nm, this could be first-hand evidence of that. It also indicates that NVIDIA has pushed GP104 closer to its limit, though that could easily be a consequence of the curve.

Given that this is our first look at Pascal, before diving into overall performance, let’s first take a look at an overclocking breakdown. NVIDIA offers 4 knobs to adjust when overclocking: overvolting (unlocking additional boost bins), increasing the power/temperature limits, the memory clock, and the GPU clock. Though all 4 will be adjusted for a final overclock, it’s often helpful to see whether it’s GPU overclocking or memory overclocking that delivers the greater impact, especially as it can highlight where the performance bottlenecks are on a card.

To examine this, we’ve gone ahead and benchmarked the GTX 1080 4 times: once with overvolting and increased power/temp limits (to serve as a baseline), once with the memory overclocked added, once with GPU overclock added, and finally with both the GPU and memory overclocks added.

GeForce GTX 1080FE Overclocking Breakdown

GeForce GTX 1080 Overclocking Performance
  Power/Temp Limit (+20%) Core (+12%) Memory (+10%) Cumulative
Tomb Raider
+3%
+4%
+1%
+10%
Ashes
+1%
+9%
+1%
+10%
Crysis 3
+4%
+4%
+2%
+11%
The Witcher 3
+2%
+6%
+3%
+10%
Grand Theft Auto V
+1%
+4%
+2%
+8%

Across all 5 games, the results are clear and consistent: GPU overclocking contributes more to performance than memory overclocking. To be sure, both contribute, but even after compensating for the fact that the GPU overclock was a bit greater than the memory overclock (12% vs 10%), we still end up with the GPU more clearly contributing. Though I am a bit surprised that increasing the power/temperature limit didn't have more of an effect.

OC: Rise of the Tomb Raider - 3840x2160 - Very High Quality (DX11)

OC: Ashes of the Singularity - 3840x2160 - Extreme Quality (DX12)

OC: Crysis 3 - 3840x2160 - Very High Quality + FXAA

OC: The Witcher 3 - 3840x2160 - Ultra Quality (No Hairworks)

OC: Grand Theft Auto V - 3840x2160 - Very High Quality

OC:  Grand Theft Auto V - 99th Percentile Framerate - 3840x2160 - Very High Quality

Overall we’re looking at an 8%-10% increase in performance from overclocking. It’s enough to further stretch the GTX 1080FE and GTX 1070FE’s leads, but it won’t radically alter performance.

OC: Load Power Consumption - Crysis 3

OC: Load Power Consumption - FurMark

OC: Load GPU Temperature - Crysis 3

OC: Load GPU Temperature - FurMark

OC: Load Noise Levels - Crysis 3

OC: Load Noise Levels - FurMark

Finally, let’s see the cost of overclocking in terms of power, temperature, and noise. For the GTX 1080FE, the power cost at the wall proves to be rather significant. An 11% Crysis 3 performance increase translates into a 60W increase in power consumption at the wall, essentially moving GTX 1080FE into the neighborhood of NVIDIA’s 250W cards like the GTX 980 Ti. The noise cost is also not insignificant, as GTX 1080FE has to ramp up to 52.2dB(A), a 4.6dB(A) increase in noise. Meanwhile FurMark essentially confirms these findings, with a smaller power increase but a similar increase in noise.

As for the GTX 1070FE, neither the increase in power consumption nor noise is quite as high as GTX 1080FE, though the performance uplift is also a bit smaller. The power penalty is just 21W at the wall for Crysis 3 and 38W for FurMark. This translates to a 2-3dB(A) increase in noise, topping out at 50.0dB for FurMark.

Power, Temperature, & Noise Final Words
Comments Locked

200 Comments

View All Comments

  • Ninhalem - Wednesday, July 20, 2016 - link

    There's 32 freaking pages in this review. Maybe people have other jobs instead of writing all day long. Did you ever think of that?

    I'll take quality and a long publishing time over crap and rushing out the door.
  • Stuka87 - Wednesday, July 20, 2016 - link

    Thanks for the extremely in depth review Ryan!
  • cknobman - Wednesday, July 20, 2016 - link

    I cannot help feel just a bit underwhelmed.

    Of course these Nvidia cards kick some major butt in games that have always favored Nvidia but I noticed that in games not specifically coded to take advantage of Nvidia and furthermore games with DX12 that these cards performance advantage is minimal at best vs an old Fury X with half the video RAM.

    Then when you take into account Vulcan API and newer DX12 games (which can be found elsewhere) you see that the prices for these cards is a tad ridiculous and the performance advantage starts to melt away.

    I am waiting for AMD to release their next "big gun" before I make a purchase decision.
    I'm rocking a 4k monitor right now and 60fps at that resolution is my target.
  • nathanddrews - Wednesday, July 20, 2016 - link

    1080 is close to being that 4K60 card, but can't quite cut it. I'm waiting for "Big Vega" vs 1080Ti before dropping any money.
  • lefty2 - Wednesday, July 20, 2016 - link

    Great review - one of the few that highlights the fact the Pascal async compute is only half as good as AMD's version. Async compute is a key feature for increasing performance in DX12 and Vulkan and that's going to allow the RX 480 to perform well against the GTX 1060
  • Daniel Egger - Wednesday, July 20, 2016 - link

    "... why the memory controller organization of GP104 is 8x32b instead of 4x64b like GM204"

    Sounds like it's the other way around.
  • Ryan Smith - Wednesday, July 20, 2016 - link

    No, that's correct. 8 32bit wide controllers rather than 4 64bit wide controllers.

    http://images.anandtech.com/doci/10325/GeForce_GTX...

    http://images.anandtech.com/doci/8526/GeForce_GTX_...
  • DominionSeraph - Wednesday, July 20, 2016 - link

    >It has taken about 2 years longer than we’d normally see

    ... for a review of a flagship card to come out
  • sgeocla - Wednesday, July 20, 2016 - link

    The old Maxwell was so optimized it was always full and didn't even need Async Compute. The new Pascal is so much more optimized that it even has time to create the "holes" in execution (not counting the ones in your pocket) that were "missing" in the old architecture to be able to benefit for Async Compute. Expect Volta to create even more holes (with hardware support) for Async Compute to fill.
  • tipoo - Wednesday, July 20, 2016 - link

    That's demonstrably untrue.

    http://www.futuremark.com/pressreleases/a-closer-l...

    Plenty of holes that could have been filled in Maxwell.

Log in

Don't have an account? Sign up now