Power, Temperature, & Noise

As always, last but not least is our look at power, temperature, and noise. Next to price and performance of course, these are some of the most important aspects of a GPU, due in large part to the impact of noise. All things considered, a loud card is undesirable unless there’s a sufficiently good reason – or sufficiently good performance – to ignore the noise.

Starting with voltages, with the latest update to GPU-Z (0.8.4) we now have a basic idea of what the R9 Fury series’ voltages are, so let’s take a look.

Radeon R9 Fury Series Voltages
R9 Fury X (Ref) Load ASUS R9 Fury Load Sapphire R9 Fury Load Sapphire R9 Fury OC Load
1.212v 1.169v 1.188v 1.212v

What we find is that the R9 Fury X tops out at 1.212v, a fairly typical voltage for a large 28nm GPU.

Meanwhile what’s of much greater interest is the difference between the two R9 Fury cards. The Sapphire Tri-X R9 Fury OC also tops out at 1.212v, indicating that it’s operating in the same voltage range as the reference R9 Fury X, and what we’d expect to see if AMD isn’t doing any power binning and just selecting Fiji chips for R9 Fury based on yields and attainable clockspeeds. The ASUS card on the other hand reports a notably lower voltage, topping out at 1.169v, 43mv below the Sapphire card.

This is an unexpected, though not unreasonable finding. We know that AMD has been carefully testing chips and more closely assigning operating voltages to them based on what the chips actually need in order to improve their energy efficiency. As a result it looks like the ASUS card ended up with a better chip as part of the overall random distribution of chips, i.e. the chip lottery. We’ll revisit this point in a little bit, but for now it’s something to keep in mind.

Moving on, let’s take a look at average clockspeeds.

Radeon R9 Fury Series Average Clockspees
Game R9 Fury X (Ref) ASUS R9 Fury Sapphire R9 Fury
Max Boost Clock 1050MHz 1000MHz 1040MHz
Battlefield 4
1050MHz
1000MHz
1040MHz
Crysis 3
1050MHz
1000MHz
1040MHz
Mordor
1050MHz
1000MHz
1040MHz
Civilization: BE
1050MHz
1000MHz
1040MHz
Dragon Age
1050MHz
1000MHz
1040MHz
Talos Principle
1050MHz
1000MHz
1040MHz
Far Cry 4
1050MHz
1000MHz
1040MHz
Total War: Attila
1050MHz
1000MHz
1040MHz
GRID Autosport
1050MHz
1000MHz
1040MHz
Grand Theft Auto V
1050MHz
1000MHz
1040MHz
FurMark
985MHz
902MHz
988MHz

All of these cards are well-cooled, and as a result they have no trouble sustaining their rated clockspeeds when running our benchmark suite games. This is the case even for the ASUS card, which has a much lower power limit, as evidenced by the lower average clockspeed under FurMark.

Idle Power Consumption

Shifting gears to power consumption, we knew at the time of the R9 Fury X that it was paying a slight idle power penalty as a result of its closed loop liquid cooler, and now we have a better idea of just what that penalty is. It essentially costs AMD another 5W at the wall to run the R9 Fury X’s pump, which means that the air-cooled R9 Fury’s idle power consumption is right in line with other air cooled cards. The fact that the ASUS and Sapphire cards are consistently 2W apart was a bit surprising, though likely a consequence of their difference PCB designs.

Load Power Consumption - Crysis 3

Load power consumption on the other hand is a poignant reminder that the R9 Fury is still a Fiji card, and that AMD can’t match the energy efficiency of NVIDIA’s Maxwell cards even under better circumstances. The Fury cards have a several percent performance lead over the GTX 980, but their power consumption in turn is much, much higher. The difference is between 62W and 109W at the wall, closer to large, power-hungry cards like the R9 Fury X and GTX 980 Ti than the smaller GTX 980 that the R9 Fury is competing with.

Overall the power gap is influenced by several factors. The R9 Fury cards run hotter than R9 Fury X, leading to more leakage. On the other hand disabling some CUs saves power, offsetting the increased leakage. But at the end of the day the R9 Fury is meant to be a 275W TBP card, just like the R9 Fury X, and that’s what we see here.

With that said, the difference between the ASUS and Sapphire cards is extremely surprising. The ASUS card has a lower power limit, but with the card sustaining 1000MHz under Crysis 3, that’s not what’s going on here. Rather we seem to be seeing the result of random chip variation quite possibly combined with ASUS’s custom PCB. Keep in mind what we said earlier about voltages, the ASUS card operates at a lower voltage than the Sapphire card, and as a result it has an advantage going into our power testing. Still, I would normally not expect a 43mv difference to lead to such significant savings.

This is a particular case where I’m curious what we’d find if we tested multiple ASUS cards, rather than looking at a sample size of 1. Would other ASUS cards have worse chips and draw more power? We’d expect so, but there may still be an advantage from ASUS’s PCB design and BIOS that need to be accounted for. At the very least it helps to close the efficiency gap between the R9 Fury and GTX 980, but it’s still not going to be enough.

Finally, since Sapphire also sent over the stock BIOS for their card we quickly tested that as well. Power consumption is down slightly thanks to slightly lower clockspeeds coupled with a lower maximum voltage of 1.188v. Still, even configured as a stock card, the ASUS card is well ahead in energy efficiency.

Load Power Consumption - FurMark

As for FurMark, we get the results more or less exactly what we were expecting. The Sapphire card with its AMD reference PCB and the high power delivery limits that entails throttles very little on FurMark, and as a result power consumption at the wall is quite high. On the other hand the ASUS card has its much lower default power limit, resulting in much heavier throttling under FurMark and keeping maximum power consumption down as well.

The end result is that the Sapphire card has a much wider range than the ASUS card, and it also indicates that the ASUS card’s power limit is likely not very far above what it takes to sustain 1000MHz under most games. The ASUS card will likely need more power to avoid power throttling if overclocked.

Idle GPU Temperature

Moving on to idle temperatures, both R9 Fury cards fare relatively well here. The fact that they have no active cooling due to their zero fan speed idle technologies means that they run a bit warmer at idle, but it’s nothing significant.

Load GPU Temperature - Crysis 3

Crysis 3 temperatures meanwhile are in-line with what these cards are designed for. The Sapphire card is designed to run at up to 75C, and that’s exactly what happens here. The ASUS card on the other hand is a bit more aggressive with its fan early on, leading to it topping out at 71C. Both, as expected, are warmer than the R9 Fury X, which is not a major problem, but it does contribute to the lower energy efficiency we’ve been seeing, particularly for the Sapphire card.

Load GPU Temperature - FurMark

FurMark on the other hand changes things slightly. The Sapphire card holds at 75C and ramps up its fan, while the ASUS card is already operating at its first fan speed limit, and as a result is allowed to increase in temperature instead. What’s holding back the ASUS card at this point and preventing it from getting warmer yet is its power limit; the card can only generate enough heat to get up to 78C with its fans running at their first limit.

Idle Noise Levels

Last but not least, we have our noise measurements, starting with idle noise. The Sapphire and ASUS cards both feature zero fan speed idle technology, which means neither card is running their fans here. As a result the cards are outright silent. What we end up measuring is the background noise, mainly the fans and pumps of our CPU’s closed loop liquid cooler. At this point zero fan speed idle technology is not cutting edge, but it is never the less impressive. High-end HTPC users, or just users looking for a very quiet card at idle should be very happy with either card.

Load Noise Levels - Crysis 3

When it came time to run our load noise testing we were expecting good things from both cards, but the results from the Sapphire Tri-X have completely blown our expectations. With sub-40dB(A) noise levels we ended up running our load noise test three different times in order to make sure there wasn’t an error in our testing methodology. There wasn’t.

What we have here then is the quietest high power air cooled card we have ever tested. In its OC configuration the Sapphire Tri-X card tops out at 38.2dB under Crysis 3, less than 2dB(A) above our noise floor and nearly 5dB quieter than the quiet R9 Fury X. Switching to its reference configuration drives noise levels down even further, to just 37.8dB(A). To put that in perspective, the Sapphire Tri-X under a gaming workload is as loud as the GTX 980 Ti is at idle. Simply put, these results are amazing.

In going over the design of Sapphire’s card there is no doubt that this is the product of several factors – not the least of which is the massive heatsink – but going back to what we said earlier about the short PCB, we’re left to wonder if that didn’t have a significant impact. By being able to blow hot air straight back (or rather, straight up), the card reduces the amount of airflow and noise being reflected against the back of the card, but it also offers a more direct cooling route that in principle reduces the amount of work the fans need to do. In any case we’ve seen Sapphire’s Tri-X cards do well before, but at 38dB(A) this is a new high water mark that is going to be difficult to beat.

Which on that note, puts the ASUS card in an awkward position. Compared to just about anything else, 46.2dB would be doing well for an open air card. But at an 8dB(A) difference between it and the Sapphire card, the difference is night and day. ASUS has to run their fans so much faster that they just can’t match what Sapphire has done. It’s a solid card, but when it comes to acoustic testing it has the misfortune of going up against some very capable competition.

Load Noise Levels - FurMark

Finally we have our noise levels under FurMark. What’s interesting here is that with the ASUS card still running at its first maximum fan speed (44%), it doesn’t get any noisier under FurMark than it does Crysis 3. The Sapphire card on the other hand does need to ramp up its fans significantly to handle the extra heat. None the less the Sapphire card still ends up being a bit quieter, topping out at 45.4dB. And when taking into consideration the significant difference in power limits between the two cards, it’s clear that the Sapphire card is remaining quieter while performing a great deal more work.

Compute Overclocking
Comments Locked

288 Comments

View All Comments

  • Midwayman - Friday, July 10, 2015 - link

    I'd love to see these two go at it again once dx12 games start showing up.
  • Mugur - Saturday, July 11, 2015 - link

    Bingo... :-). I bet the whole Fury lineup will gain a lot with DX12, especially the X2 part (4 + 4 GB won't equal 4 as in current CF). The are clearly CPU limited at this point.
  • squngy - Saturday, July 11, 2015 - link

    I don't know...

    Getting dx12 performance at the cost of dx11 performance sounds like a stupid idea this soon before dx12 games even come out.

    By the time a good amount of dx12 games come out there will probably be new graphics cards available.
  • thomascheng - Saturday, July 11, 2015 - link

    They will probably circle around and optimize things for 1080p and dx11, once dx12 and 4k is at a good place.
  • akamateau - Tuesday, July 14, 2015 - link

    DX12 games are out now. DX12 does not degrade DX11 performance. In fact Radeon 290x is 33% faster than 980 Ti in DX12. Fury X just CRUSHES ALL nVIDIA silicon with DX12 and there is a reason for it.

    Dx11 can ONLY feed data to the GPU serially and sequencially. Dx12 can feed data Asynchronously, the CPU send the data down the shader pipeline WHEN it is processed. Only AMD has this IP.
  • @DoUL - Sunday, July 19, 2015 - link

    Kindly provide link to a single DX12 game that is "out now".

    In every single review of the GTX 980 Ti there is this slide of DX12 feature set that the GTX 980 Ti supports and in that slide in all the reviews "Async Compute" is right there setting in the open, so I'm not really sure what do you mean by "Only AMD has this IP"!

    I'd strongly recommend that you hold your horses till DX12 games starts to roll out, and even then, don't forget the rocky start of DX11 titles!

    Regarding the comparison you're referring to, that guy is known for his obsession with mathematical calculations and synthetic benchmarking, given the differences between real-world applications and numbers based on mathematical calculations, you shouldn't be using/taking his numbers as a factual baseline for what to come.
  • @DoUL - Sunday, July 19, 2015 - link

    My Comment was intended as a reply to @akanateau
  • OldSchoolKiller1977 - Sunday, July 26, 2015 - link

    You are an idiotic person, wishful think and dreams don't make you correct. As stated please provide a link to these so called DX12 games and your wonderful "Fury X just CRUCHES ALL NVidia" statement.
  • Michael Bay - Sunday, July 12, 2015 - link

    As long as there is separate RAM in PCs, memory argument is moot, as contents are still copied and executed on in two places.
  • akamateau - Tuesday, July 14, 2015 - link

    Negative. Once Graphic data is processed and sent to the shaders it next goes to VRAM or video ram.

    System ram is what the CPU uses to process object draws. Once the objects are in the GPU pipes system ram is irrelevant.

    IN fact that is one of AMD's stacked memory patents. AMD will be putting HBM on APU's to not only act as CPU cache but HBM video ram as well. They have patents for programmable HBM using FPGA's and reconfigurable cache memory HBM as well.

    Stacked memory HBM can also be on the cpu package as a replacement for system ram. Can you imagine how your system would fly with 8-16gb of HBM instead of system ram?

Log in

Don't have an account? Sign up now