Overclocking

Finally, no review of a high-end video card would be complete without a look at overclocking performance.

As was the case with the R9 Fury X two weeks ago, overclockers looking at out of the box overclocking performance are going to come away disappointed with the R9 Fury cards. While cooling and power delivery are overbuilt on both the Asus and Sapphire cards, the R9 Fury is still very restricted when it comes to overclocking. There is no voltage control at this time (even unofficial) and the card’s voltage profile has been finely tuned to avoid needing to supply the card with more voltage than is necessary. As a result the card has relatively little overclocking potential without voltage adjustments.

Radeon R9 Fury Series Overclocking
  Ref. R9 Fury X ASUS R9 Fury Sapphire R9 Fury OC
Boost Clock 1125MHz 1075MHz 1100MHz
Memory Clock 1Gbps (500MHz DDR) 1.1Gbps (550MHz DDR) 1.1Gbps (550MHz DDR)
Power Limit 100% 115% 100%
Max Voltage 1.212v 1.169v 1.212v

Neither R9 Fury card is able to overclock as well as our R9 Fury X, indicating that these are likely lower quality (or lower headroom) chips. Ultimately we’re able to get another 75MHz out of the ASUS, for 1075MHz, and another 60MHz out of the Sapphire, for 1100MHz.

Meanwhile with unofficial memory overclocking support now attainable via MSI Afterburner, we’ve also tried our hand at memory overclocking. There’s not a ton of headroom here before artifacting sets in, but we were able to get another 10% (50MHz) out of both R9 Fury cards.

Using our highest clocking card as a reference point, the Sapphire card, the actual performance gains are in the 7-10% range, with an average right up the middle at 8% over a reference clocked R9 Fury. This is actually a bit better than the R9 Fury X and its 5% performance gains, however it’s still not going to provide a huge difference in performance. We’d need to be able to overclock to better than 1100MHz to see any major overclocking gains on the R9 Fury cards.

Power, Temperature, & Noise Final Words
Comments Locked

288 Comments

View All Comments

  • bill.rookard - Friday, July 10, 2015 - link

    Impressive results, especially by the Sapphire card. The thing I'm glad to see is that it's such a -quiet- card overall. That bodes well for some of the next releases (I'm dying to see the results of the Nano) and bodes well for AMD overall.

    Two things I'd like to see:

    1) HBM on APU. Even if it were only 1GB or 2GB with an appropriate interface (imaging keeping the 4096 bit interface and either dual or quad-pumping the bus?). The close location of being on-die and high speed of the DRAM would be a very, VERY interesting graphics solution.

    2) One would expect that with the cut down on resources, there would have been more of a loss in performance. On average, you see a 7-8% drop in speed after a loss of 13-14% cut in hardware resources and a slight drop in clock speeds. So - where does that mean the bottleneck in the card is? It's possible that something is a bit lopsided internally (it does however perform exceptionally well), so it would be very interesting to tease out the differences to see whats going on inside the card.
  • mr_tawan - Friday, July 10, 2015 - link

    It would be very interesting to run HBM as the system ram instead of DDR on APU. 4GB (for the 1) wouldn't be a lot and may choke on heavy work load, but for casual user (and tablet uses) that's probably enough.

    It would also allow smaller machine than NUC form factor, I think.
  • looncraz - Friday, July 10, 2015 - link

    HBM wouldn't be terribly well suited for system RAM due to its comparatively low small-read performance and physical form factor. On an APU, for example, it would probably be best used as a single HBM[2] chip on a 1024-bit bus. Probably just 1 or 2GB, largely dedicated to graphics. That is 128GB/s with HBM1 (but 1GB max), 256GB/s with HBM2 (with, IIRC, 4GB max).

    For a SoC, though, such as the NUC form factor, as you mentioned, it is potentially a game changer only AMD can deliver on x86. Problem is that the net profit margins in that category are quite small, and AMD needs to be chasing higher net margin markets (net margin being a simple result of market volume, share, and product margin).

    I'd love to see it, though, for laptops. And with Apple and AMD being friendly, we may end up seeing it. As well as probably seeing it find its way into the next generation of consoles.
  • Oxford Guy - Saturday, July 11, 2015 - link

    Given the high prices Intel is charging for its NUC systems are you really certain it's not profitable? Perhaps sales aren't good because they're overpriced.
  • Stuka87 - Friday, July 10, 2015 - link

    The only way to keep the 4096bit bus would be to use four HBM chips, and I highly doubt this would be the case. I am thinking an APU would use either a single HBM chip, or possibly two. The performance boost would still be huge.
  • ajlueke - Friday, July 10, 2015 - link

    1) I can't imagine we won't see this. APU scaling with RAM speed was pretty well documented, I would be surprised if there were socket AM4 motherboards that incorporated some amount of HBM directly. Also, AMD performs best against NVidia at 4K, suggesting that Maxwell may be running into a memory bandwidth bottleneck itself. It will be interesting to see how Pascal performs when you couple a die-shrink with the AMD developed HBM2.
    2) It does suggest that Fiji derives far more benefit from faster clocks versus more resources. That makes the locked down voltages for the Fury X even more glaring. You supply a card that is massively overpowered, with 500W of heat dissipation but no way to increase voltages to really push the clock speed? I hope we get custom BIOS for that card soon.
  • silverblue - Saturday, July 11, 2015 - link

    As regards APU scaling, it's a tough one. More bandwidth is good, however scaling drops above 2133MHz which shows you'd need more hardware to consume it. Would you put in more shaders, or ROPs? I'd go for the latter - don't APUs usually top out at 8 ROPs? Sure, add in more bandwidth, but at the very least, increase how much the APU can actually draw. The HD 4850 had 32 TMUs (like the 7850K) but 16 ROPs, which is double that on offer here.

    I keep seeing complaints about AMD's ROP count, so perhaps there's some merit to them.
  • Nagorak - Sunday, July 12, 2015 - link

    It's hard to say what the bottleneck is with memory scaling on APUs. It could be something related to the memory controller built into the CPU rather than the GPU not having the resources to benefit.
  • silverblue - Monday, July 13, 2015 - link

    Isn't there a 256-bit Radeon Memory Bus link between memory and the GPU? Just a question.
  • Stuka87 - Friday, July 10, 2015 - link

    Is it just me, or is the 290X faster now than it used to be when compared to the 980? Perhaps the 15.7 drivers offered some more performance?

Log in

Don't have an account? Sign up now