Power, Temperature, & Noise

Last but not least as always is our look at the power consumption, temperatures, and acoustics. As there isn’t a reference GTX 560, we’re working with what we have: the ASUS GTX 560 DirectCU II Top. For the sake of completeness we’re including our results for power/temp/noise at both the Base (810MHz) and Mid (850MHz) on the ASUS card. However if ASUS is goosing the voltage a bit to hit 925MHz, then it’s likely we’re drawing a bit more power here than a card specifically targeted for those performance levels.

GeForce GTX 460/560 Series Load Voltage
GTX 460 GTX 560 Ti ASUS GTX 560 ASUS GTX 560 OC
1.025v 1.0v 1.037v 1.062v

Looking at voltage quickly, ASUS is running the GTX 560 Top at 1.037v. This is a bit more than any other GF114/GF104 card that we’ve seen, but not by a great deal. The voltage difference between the GTX 560 Top and the reference GTX 560 Ti does mean that any power benefits of having a SM disabled are wiped out. In other words, the GTX 560 Top can offer GTX 560 Ti-like performance, but at GTX 560 Ti-like power consumption.

Idle power consumption looks very good here. The GTX 560 Ti already did well, and now the GTX 560 does even better. The difference ultimately comes down to the power savings realized by disabling a SM.

Starting with our sample card, the ASUS GTX 560, we’ve already hinted at the fact that power consumption between these heavily factory overclocked cards and the GTX 560 Ti will end up being very similar, in accordance with their similar performance. The results deliver on that concept, with the ASUS GTX 560 and the GTX 560 Ti being separated by only 7W in the ASUS GTX 560’s favor. Overclocking doesn’t have the expected ramp up in power consumption however, as even with the slightly higher clocks and higher voltage, power consumption only rises by 10W for the whole system.

As for our simulated GTX 560 Base and Mid, we can’t say too much. Based on NVIDIA’s specs and the better leakage properties of GF114, there’s no reason why a GTX 560 built for those clocks shouldn’t be able to achieve power consumption similar to (if not better than) the GTX 460 series. We’d get far better data from a suitably lower performing GTX 560 card.

One thing that is clear however is that unless power consumption on lower clocked GTX 560s was more than 20W lower, AMD’s general advantage in power consumption is unchallenged. The same can be said for the GTX 6950, which consumes nearly 18W less than the ASUS GTX 560, even though the latter is often the performance laggard.

Under FurMark the ASUS GTX 560 actually does worse than the GTX 560 Ti, likely due to the ASUS card’s lack of overcurrent protection circuitry and the realization of the full impact of operating at a higher voltage. The difference isn’t this pronounced in games, but FurMark hits all the right notes. Along this same train of thought we see our overclocked ASUS GTX 560 consuming a further 20W beyond what the card consumes under factory settings. The overclocked ASUS GTX 560 usually could beat the GTX 560 Ti, but the power consumption is a major tradeoff.

As for our simulated GTX 560 Mid and Base cards, the results are of a similar nature as our Crysis power results. Power consumption is higher than both the GTX 460 series and AMD’s Radeon HD 6800 series due to the voltages involved.

Idle temperatures are largely a function of the cooler being used. The GTX 560 Ti did exceptionally well here, and it’s nearly impossible to compete with it. At 33C the ASUS GTX 560 is among the coolest cards in our regular charts, and yet it can’t catch the GTX 560 Ti.

When looking at ASUS cards, we often see them favoring aggressive cooling over noise. We’ll get to noise in a bit, but certainly it looks like they have cooling as if not more aggressive than the reference GTX 560 Ti. At 71C the ASUS GTX 560 and the GTX 560 Ti are tied, and are both well below a number of other cards in temperature; an impressive feat given the performance we’ve seen earlier. Our simulated cards are a bit cooler, but they would probably be even better if they were at a lower voltage.

Unfortunately FurMark doesn’t look as good as Crysis, thanks in part to AMD’s use of PowerTune on the 6900 series, and the higher power consumption due to ASUS’s overvolting making itself felt. 84C under Furmark is not at all bad as it’s not even close to any sort of critical GPU temperature, but it’s not quite chart topping. It’s also well off what we’ve seen the GTX 560 Ti do, which is 5C cooler at 79C. Further overclocking and overvolting on the ASUS GTX 560 does dive the temperature up to 89C, which means at 1.062v we’re probably applying as much voltage as we can reasonably get away with.

As for our simulated cards, both the GTX 560 Base and GTX 560 Mid are well above their GTX 460 counterparts. Part of this goes back to power consumption, but it also involves just how different their respective coolers are.

It’s rare to see a card not bottom out on our idle noise testing, and the ASUS GTX 560 doesn’t disappoint. At idle it’s whisper quiet, and it can’t be distinguished from our noise floor.

Last but not least is our look at load noise, where ASUS’s generally aggressive cooling finally becomes quantified. At 54.7dB it’s about the middle of the pack, and actually beats the Radeon HD 6870. But we’ve seen the reference GTX 560 Ti complete the same test at 8dB less – even if we could equalize the power consumption the GTX 560 Ti reference cooler seems to have an edge over ASUS’s DirectCU II cooler when it comes to noise under load. Cutting down the clocks to Base or Mid levels helps this some, but then rendering performance shrinks away from the GTX 560 Ti.

Compute Performance Final Thoughts


View All Comments

  • TheJian - Wednesday, May 18, 2011 - link

    See my other posts. Nvidia finally got multithreaded rendering finished in their drivers (which should affect many games now, it's not GAME specific). Expect AMD to get theirs done soon. This isn't Civ5 or Anandtech favoring NV, it's just the beat AMD to the punch in getting drivers finished. If AMD takes another year to get their drivers done, I'm glad they report this. I hope AMD gets them done soon, or the next set of cards that get benched might show quite a few games with AMD bunched at the bottom of the list.

    NOTE: this is a DRIVER issue, not game issue. Both sides have been working on getting this in their drivers for a while. It's about time :) The game had this in it all the time (many other too, get ready for speedups if you own NV and running 2.75 drivers (whatever is latest from NV). Unfortunately my 5850 has to wait for AMD. :(
  • JarredWalton - Tuesday, May 24, 2011 - link

    You know what the best part is about Civ5? AMD is the one that gave out copies of the game to reviewers. Yup -- that and F1 2010. Reply
  • L. - Thursday, May 19, 2011 - link

    Errr/ metacritic lol ?

    We're talking benchmarking here, not playing the game.

    AMD being poor is their problem, we shouldn't care ;)

    Besides, the way people rate on metacritic or any critic source for anything is at most a relative indicator of how people who take the time to vote feel about stuff... doesn't help that much does it ?

    Crysis 2 is NOT in the same series as Crysis 1. If you don't know why, read some more about it.
  • L. - Thursday, May 19, 2011 - link

    Two words for you mate, Bench and Mark
    The purpose of benchmarking is to get a relative idea of the performance of a component, not to test every little game out there, because of that reviewers attempt to have a most relevant panel of games/ benchmarks to test the gfx cards.

    Crysis 2 is not (yet) a relevant benchmark. Maybe when they're done writing the engine for PC's it will be, but now it's just a worthless console port.

    IF you think they're lazy, just post a list of the games you would use to benchmark and ask people how useful they find those.
  • Spoelie - Wednesday, May 18, 2011 - link

    Metro 2033 is a game that requires the force scaling flag I believe. It ignores the scaling settings in AMD's drivers on windows 7 at least..

    Coloring is wrong on the Civ5 graph (last one)
  • GeorgeH - Wednesday, May 18, 2011 - link

    Taken out of the noise of the other comment stream:

    "RE: Time to change the tests by Ryan Smith on Tuesday, May 17, 2011
    The test suite is due for a refresh, and will either be updated at the end of this month or next month once we build our new SNB testbed."

    Weren't you waiting for SNB-E? Isn't that a Q4 release? Or by "SNB" do you mean "Bulldozer" and know something that we don't?

    You've got me all curious and maybe excited and more curious and now I-don't-know-what-to-think.

Log in

Don't have an account? Sign up now