Synthetics

As always we’ll also take a quick look at synthetic performance. As we briefly discussed in our look at the GCN 1.2 architecture these tests mainly serve as a canary for finding important architectural changes, and one of these tests in particular has been significantly impacted by AMD’s newest round of architectural improvements.

Synthetic: TessMark, Image Set 4, 64x Tessellation

At the x64 tessellation factor we see the R9 285 spit out 134fps, or equivalent to roughly 1.47B polygons/second. This is as compared to 79fps (869M Polys/sec) for the R9 290, and 68fps (748M Polys/sec) for the R9 280. One of the things we noted when initially reviewing the R9 290 series was that AMD’s tessellation performance didn’t pick up much in our standard tessellation benchmark (Tessmark at x64) despite the doubling of geometry processors, and it looks like AMD has finally resolved that with GCN 1.2’s efficiency improvements. As this is a test with a ton of small triangles, it looks like we’ve hit a great case for the vertex reuse optimizations.

Moving on, we have our 3DMark Vantage texture and pixel fillrate tests, which present our cards with massive amounts of texturing and color blending work. These aren’t results we suggest comparing across different vendors, but they’re good for tracking improvements and changes within a single product family.

Synthetic: 3DMark Vantage Texel Fill

With AMD maintaining their same texture units and same tex:FP32 ratio for Tonga, the end result is that R9 285’s texturing performance is virtually identical to R9 280’s. Ignoring any possibility of caching or bandwidth bottlenecking for the moment, R9 285 can push texels just as well as R9 280 could.

Synthetic: 3DMark Vantage Pixel Fill

Unlike our texel test, AMD’s delta color compression technology introduced on GCN 1.2 has an incredible impact on R9 285’s pixel throughput. This pixel test is normally memory bandwidth bound, providing something that approaches a best case scenario for AMD’s compression technology. As a result despite possessing nearly 30% less memory bandwidth than the R9 280, the R9 285 tops our charts at 19.9 GPix/sec, blowing past the R9 280 by 68%. Even the R9 290 with its 512-bit memory bus and doubled ROP count still falls short here by over 3GPix/sec, or 16%.

This benchmark in a nutshell is why AMD can deliver the average performance of the Tahiti based R9 280 without Tahiti’s memory bandwidth. By improving their color compression to this point AMD can significantly reduce their memory bandwidth requirements on GCN 1.2, allowing them to do more with less. In real games the result won’t be anywhere near this remarkable since this is a pure pixel fillrate test, but it goes to show that AMD has been able to neutralize their memory bandwidth deficit in graphics workloads.

GRID 2 Compute
Comments Locked

86 Comments

View All Comments

  • Samus - Wednesday, September 10, 2014 - link

    Am I missing something or is this card slower than the 280...what the hell is going on?
  • tuxRoller - Wednesday, September 10, 2014 - link

    Yeah, you're missing something:)
  • Samus - Thursday, September 11, 2014 - link

    BF4 its about 4% slower.
  • Kenshiro70 - Wednesday, September 10, 2014 - link

    "something of a lateral move for AMD, which is something we very rarely see in this industry"

    Really? Seems like the industry has been rebadging for the last two release cycles. How about starting to test and show results on 4k screens? 60Hz ones are only $500 now, and that will put a little pressure on the industry to stop coasting. I have no intention of spending money on a minor bump up in specs. Bitcoin mining demand can't last forever.
  • tuxRoller - Wednesday, September 10, 2014 - link

    Error page 4: chart should read "lower is better"
  • jeffrey - Wednesday, September 10, 2014 - link

    Saw this too, the Video Encode chart Ryan.

    Congrats btw!
  • Ryan Smith - Thursday, September 11, 2014 - link

    Whoops. Thanks.
  • yannigr2 - Wednesday, September 10, 2014 - link

    Great article and review.

    The only bad news here I think is Mantle.

    But on this matter, about Mantle, maybe a slower processor could show less of that performance drop or even keep performing better than DirectX11. Maybe one more test on a slower core, on an FX machine?
  • mapesdhs - Wednesday, September 10, 2014 - link

    What were AMD thinking? How can the 285 be a replacement for the 280, given its
    reduced VRAM, while at the same time AMD is pushing Mantle? Makes no sense at all.

    Despite driver issues, I'd kinda gotten used to seeing AMD be better than NVIDIA in
    recent times for VRAM capacity. A new card with only 2GB is a step backwards. All
    NVIDIA has to do is offer a midrange Maxwell with a minimum 4GB and they're home.
    No idea if they will. Time will tell.

    Ian.
  • Alexvrb - Wednesday, September 10, 2014 - link

    There you have it, and with no issues with boost. Sorry Chizow, so much for that. :P

    Thanks for the in-depth review, Ryan. It appears that power consumption is going to vary from implementation to implementation. Lacking a reference model makes it tricky. Another review I read compared Gigabyte's Windforce OC 285 to a similarly mild OC'd 280, finding a substantial difference in the 285's favor.

Log in

Don't have an account? Sign up now