Meet The Asus Radeon R7 260

Our other card of the day is our R7 260 sample from AMD, which comes in the form of a complete retail card: Asus’s Radeon R7 260. This is a standard retail card, featuring a solid design but no factory overclock or other frills.

Surprisingly for a 95W card, Asus’s card is a dual fan open air design. Based on a variation of their dual fan coolers, Asus utilizes a relatively simple aluminum heatsink directly mounted to the Bonaire GPU beneath. This heatsink has a large base that serves to cover the RAM, but not the VRMs towards the front of the card, and mushrooms out at the top to form a larger surface for the dual fans to cool. Truth be told we were pleasantly surprised by this design; these larger dual fan designs are uncommon for sub-100W cards, and even with the relatively simple heatsink it’s essentially oversized for the GPU in question, though as we’ll see in our noise results this is clearly to the benefit of the user.

As a result of using such a large cooler on such a small board, the Asus R7 260’s cooler significantly overhangs the PCB. The PCB itself is just 6.8” long, while the cooler extends a further 1.9” to give the card a total length of 8.7”. As is usual for Asus, the card feature’s Asus’s Super Alloy Power discrete electrical components for enhanced durability. Meanwhile the fact that this is closer to a card strapped to a cooler than a cooler strapped to a card doesn’t do Asus any favors, especially since the GPU is towards the rear of the card. The short length of the card ensures it’s rigid enough, but there’s some opportunity for flexing towards the front of the card.

For Asus’s power connectivity, the single 6-pin PCIe power socket is found at the end of the card, orientated parallel to the PCB despite the significant overhang of the cooler. To make up for this, Asus has once again reversed the PCIe power socket so that the tab on the plug faces inwards instead of outwards, which makes this design practical as the cooler no longer blocks the tab.

As for Asus’s display I/O, Asus is using a simpler port layout that occupies just a single slot, presumably so that this PCB is capable of being used on single-slot designs if necessary. This results in the card having 1x DL-DVI, 1x HDMI, and happily enough for such a low-end card, 1x DisplayPort, as opposed to a VGA port. This gives the Asus card the ability to drive three digital displays at once for Eyefinity, or even a single 4K display if we’re talking about simple desktop work.

Meanwhile on the software side of things the R7 260 comes with Asus’s standard GPUTweak software utility. GPUTweak is a very competent overclocking suite that offers all of the overclocking and monitoring functionality we’ve come to expect from a good overclocking utility, including a wide array of monitoring options and support for GPU voltage control. Asus’s taste in skins is unfortunate – a low contrast red on black – but otherwise the UI itself is similarly solid. To that end GPU Tweak won’t match Afterburner on some of its more fringe features such as recording and overlays, but as a pure overclocking utility it stands up rather nicely.

Wrapping things up, as one of the only two R7 260 graphics cards currently Asus is both enjoying and being disrupted by the lack of sensible pricing among R7 260 cards. At a current retail price of $139 the Asus R7 260 is a full $30 (28%) over what should be a $109 MSRP for an R7 260 card, and $15 more expensive than the alternative MSI card. More importantly, it’s currently just as expensive as the more powerful R7 260X, which puts this card in an unfortunate spot since you can easily buy a more powerful card for less. Asus can enjoy a small premium from a good design and their 3 year warranty, but this is an especially treacherous position if R7 260X prices quickly come down to $119.

Finally, on a quick technical note we do want to point out that we have encountered one minor oddity with the Asus R7 260 that as of this writing is still being looked into by AMD. The card we received has its GPU idle clockspeed at 550MHz, instead of the 300MHz clockspeed that is common for all other AMD GCN cards, including their other Bonaire cards. The ramifications of this are minimal as it doesn’t affect the load performance of the card in any way, but it does mean the card is technically running at a higher clockspeed than it should at idle, which can affect idle power consumption. We’re seeing 74W at the wall, the same as our reference R7 260X, but our GPU testbed is admittedly not well suited to picking up small fluctuations in idle power consumption like this on such a low powered card. In any case we don’t believe it to be a dealbreaker, but AMD is currently looking into it to try to determine what’s going on.

Meet The Sapphire Radeon R7 265 The Test
Comments Locked

52 Comments

View All Comments

  • edzieba - Thursday, February 13, 2014 - link

    Are Anandtech considering a switch from average framerates to latency/frame-rating (either with Fraps or FCAT)?
  • Ryan Smith - Thursday, February 13, 2014 - link

    Frame pacing is an additional tool we run from time to time as is appropriate, but it's not something we'll use for every review. Frame pacing is largely influenced by drivers and hardware, neither of which shift much on a review-by-review basis. So it's primarily reserved for multi-GPU articles and new architectures as appropriate.

    And especially in the case of single-GPU setups, there's not much to look at. None of these cards has trouble delivering frames at a reasonably smooth pace.

    http://www.anandtech.com/bench/GPU14/873
  • HisDivineOrder - Thursday, February 13, 2014 - link

    Yeah, that's what you guys said before the whole frame latency thing broke, too. It's a shame you aren't doing proper monitoring to catch it the first time and are setting up a scenario where it flies under the radar yet again the next time AMD decides to get lax on making drivers.

    Then again, this article is in red, right? AMD News is right next to it. Hell, even the comment button is red. I'm guessing the AMD overlords wouldn't like it very much if you were constantly harping on something they dropped the ball on so completely that their competitor had to slowly explain to them how to even see the problem and then how to fix it.
  • gdansk - Thursday, February 13, 2014 - link

    It's a shame. I'm with your argument. AnandTech should try to include as many indicative benchmarks as possible. At times FCAT is indicative.

    But sadly, calling someone a shill with only coincidence is no better than libel. You have made an unsubstantiated allegation. It is decidedly unscientific to insult one's professional integrity with mere coincidental insinuations and no evidence. Why would you do that?
  • Death666Angel - Thursday, February 13, 2014 - link

    So they are in the pocket of nVidia, Intel, AMD, Android AND Apple? Wow, those companies must really be idiots then.
  • Gigaplex - Thursday, February 13, 2014 - link

    I don't know where you got all the other brands from, but technically yes Ars is in the pockets of AMD. See http://www.anandtech.com/portal/amd - this is sponsored by AMD.
  • Gigaplex - Thursday, February 13, 2014 - link

    Bah, AnandTech, not Ars
  • Death666Angel - Thursday, February 13, 2014 - link

    I know _that_. But he is clearly insinuating that their opinions are bought by AMD. And since products from all those companies I listed (who are all competitors) regularly get recommendations, and Anandtech gets then accused of being paid shills, I find it funny that anyone thinks that is true. If they are bought by AMD as suggested, how come they don't come up with a benchmark track that makes AMD CPUs shine? Or how come they slammed the R9 so much for the noise? It's all pretty silly.
  • nader_21007 - Friday, February 14, 2014 - link

    It seems that it hurts you how come this site is not biased and doesn't admire every thing Nvidia, like other sites? well you can go read Tom's Hardware, WCCFtech and every other hardware site, and be sure they will satisfy your needs.
  • zodiacsoulmate - Friday, February 14, 2014 - link

    Yea, it's like trying to compare samsung to apple again, sure you can say there is no way to compare which one is better hardware considered, the user experience is just not on pair...

Log in

Don't have an account? Sign up now