Final Words

Bringing this video card review to a close, we’ll start off with how the R9 Fury compares to its bigger sibling, the R9 Fury X. Although looking at the bare specifications of the two cards would suggest they’d be fairly far apart in performance, this is not what we have found. Between 4K and 1440p the R9 Fury’s performance deficit is only 7-8%, noticeably less than what we’d expect given the number of disabled CUs.

In fact a significant amount of the performance gap appears to be from the reduction in clockspeed, and not the number of CUs. And while overclocking back to R9 Fury X clockspeeds can’t recover all of the performance, it recovers a lot of it. This implies that Fiji on the whole is overweight on shading/texturing resources, as it’s not greatly impacted by having some of those resources cut off.

Consequently I can see why AMD opted to launch the R9 Fury X and R9 Fury separately, and to withhold the latter’s specifications until now, as this level of performance makes R9 Fury a bit of a spoiler for R9 Fury X. 7-8% makes R9 Fury notably slower than R9 Fury X, but it’s also $100 cheaper, or to turn this argument on its head, the last 10% or so that the R9 Fury X offers comes at quite the price premium. This arguably makes the R9 Fury the better value, and not that we’re complaining, but it does put AMD in an awkward spot.

As for the competition, that’s a bit more of a mixed bag. R9 Fury X had to compete with GTX 980 Ti but couldn’t surpass it, which hurt it and make the GTX the safer buy. On the other hand R9 Fury needs to compete with just the older GTX 980, and while it’s by no means a clean sweep for AMD, it’s a good outcome for AMD. The R9 Fury offers between 8% and 17% better performance than the GTX 980, depending on if we’re looking at 1440p or 4K. I don’t believe the R9 Fury is a great 4K card – if you really want 4K, you really need more rendering power at this time – but even at 1440p this is a solid performance lead.

Along with a performance advantage, the GTX 980 is also better competition for the R9 Fury (and Fiji in general) since the GTX 980 is only available with 4GB of VRAM. This negates the Fiji GPU’s 4GB HBM limit, which is one of the things that held back the R9 Fury X against the GTX 980 Ti. As a result there are fewer factors to consider, and in a straight-up performance shootout with the GTX 980 the R9 Fury is 10% more expensive for 8%+ better performance. This doesn’t make either card a notably better value, but makes the R9 Fury a very reasonable alternative to the GTX 980 on a price/performance basis.

The one area where the R9 Fury struggles however is power efficiency. GTX 980’s power efficiency is practically legendary at this point; R9 Fury’s is not. Even the lower power of our two R9 Fury cards, the ASUS STRIX, can’t come close to GTX 980’s efficiency. And that’s really all there is to that. If energy efficiency doesn’t matter to you then the R9 Fury’s performance is competitive, otherwise GTX 980 is a bit slower, a bit cheaper, and uses a lot less power. That said, AMD’s partners do deserve some credit for keeping their acoustics well under control despite the high power and heat load. It’s not an apples-to-apples comparison against the reference GTX 980 and its blower, but at the very least picking R9 Fury over GTX 980 doesn’t mean you have to pick a loud card as well.

And that brings us to the third aspect of this review, which is comparing the R9 Fury cards from Sapphire and ASUS. Both partners have come to the plate with some very good open air cooled designs, and while it’s a bit unusual for AMD to launch with so few partners, what those partners have put together certainly paint R9 Fury in a positive light.

Picking between the two ends up being a harder task than we expected, in part because of how different they are at times. From a performance perspective the two cards offer very similar performance, with Sapphire’s mild factory overclock giving them only the slightest of edges, which is more or less what we expected.

However the power and acoustics situation is very different. On its own the ASUS STRIX’s acoustics would look good, but compared to the Sapphire Tri-X’s deliciously absurd acoustics it’s the clear runner-up. On the other hand the ASUS card has a clear power efficiency advantage of its own, but I’m not convinced that this isn’t just a byproduct of the ASUS card randomly receiving a better chip. As a result I’m not convinced that this same efficiency advantage exists between all ASUS and Sapphire cards; ASUS’s higher voltage R9 Fury chips have to go somewhere.

In any case, both are solid cards, but if we have to issue a recommendation then it’s hard to argue with the Sapphire Tri-X’s pricing and acoustics right now. It’s the quietest of the R9 Fury cards, and it’s slightly cheaper as well. Otherwise ASUS’s strengths lie more on their included software and their reputation for support than in their outright performance in our benchmark suite.

And with that, we wrap up our review of the second product in AMD’s four Fiji launches. The R9 Fury was the last product with a scheduled launch date, however AMD has previously told us that the R9 Nano will launch this summer, meaning we should expect it in the next couple of months. With a focus on size and efficiency the R9 Nano should be a very different card from the R9 Fury and R9 Fury X, which makes us curious to see just what AMD can pull off when optimizing for efficiency over absolute performance. But that will be a question for another day.

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