GL/DXBenchmark 2.7 & Final Words

While the 3DMark tests were all run at 720p, the GL/DXBenchmark results run at roughly 2.25x the pixel count: 1080p. We get a mixture of low level and simulated game benchmarks with GL/DXBenchmark 2.7, the former isn't something 3DMark offers across all platforms today. The game simulation tests are far more strenuous here, which should do a better job of putting all of this in perspective. The other benefit we get from moving to Kishonti's test is the ability to compare to iOS and Windows RT as well. There will be a 3DMark release for both of those platforms this quarter, we just don't have final software yet.

We'll start with the low level tests, beginning with Kishonti's fill rate benchmark:

GL/DXBenchmark 2.7 - Fill Test (Offscreen)

Looking at raw pixel pushing power, everything post Apple's A5 seems to have displaced NVIDIA's GeForce 6600. NVIDIA's Tegra 3 doesn't appear to be quite up to snuff with the NV4x class of hardware here, despite similarities in the architectures. Both ARM's Mali-T604 (Nexus 10) and ImgTec's PowerVR SGX 554MP4 (iPad 4) do extremely well here. Both deliver higher fill rate than AMD's Radeon HD 6310, and in the case of the iPad 4 are capable to delivering midrange desktop GPU class performance from 2004 - 2005.

Next we'll look at raw triangle throughput. The vertex shader bound test from 3DMark did some funny stuff to the old G7x based architectures, but GL/DXBenchmark 2.7 seems to be a bit kinder:

GL/DXBenchmark 2.7 - Triangle Throughput, Fragment Lit (Offscreen)

Here the 8500 GT definitely benefits from its unified architecture as it is able to direct all of its compute resources towards the task at hand, giving it better performance than the 7900 GTX. The G7x and NV4x based architectures unfortunately have limited vertex shader hardware, and suffer as a result. That being said, most of the higher end G7x parts are a bit too much for the current crop of ultra mobile GPUs. The midrange NV4x hardware however isn't. The GeForce 6600 manages to deliver triangle throughput just south of the two Tegra 3 based devices (Surface RT, Nexus 7).

Apple's iPad 4 even delivers better performance here than the Radeon HD 6310 (E-350).

ARM's Mali-T604 doesn't do very well in this test, but none of ARM's Mali architectures have been particularly impressive in the triangle throughput tests.

With the low level tests out of the way, it's time to look at the two game scenes. We'll start with the less complex of the two, Egypt HD:

GL/DXBenchmark 2.5 - Egypt HD (Offscreen)

Now we have what we've been looking for. The iPad 4 is able to deliver similar performance to the GeForce 7900 GS, and 7800 GT, which by extension means it should be able to outperform a 6800 Ultra in this test. The vanilla GeForce 6600 remains faster than NVIDIA's Tegra 3, which is a bit disappointing for that part. The good news is Tegra 4 should be somewhere around high-end NV4x/upper-mid-range G7x performance in this sort of workload. Again we're seeing Intel's HD 4000 do remarkably well here. I do have to caution anyone looking to extrapolate game performance from these charts. At best we know how well these GPUs stack up in these benchmarks, until we get true cross-platform games we can't really be sure of anything.

For our last trick, we'll turn to the insanely heavy T-Rex HD benchmark. This test is supposed to tide the mobile market over until the next wave of OpenGL ES 3.0 based GPUs take over, at which point GL/DXBenchmark 3.0 will step in and keep everyone's ego in check.

GL/DXBenchmark 2.7 - T-Rex HD (Offscreen)

T-Rex HD puts the iPad 4 (PowerVR SGX 554MP4) squarely in the class of the 7800 GT and 7900 GS. Note the similarity in performance between the 7800 GT and 7900 GS indicates the relatively independent nature of T-Rex HD when it comes to absurd amounts of memory bandwidth (relatively speaking). Given that all of the ARM platforms south of the iPad 4 line have less than 12.8GB/s of memory bandwidth (and those are the platforms these benchmarks were designed for), a lack of appreciation for the 256-bit memory interfaces on some of the discrete cards is understandable. Here the 7900 GTX shows a 50% increase in performance over the 7900 GS. Given the 62.5% advantage the GTX holds in raw pixel shader performance, the advantage makes sense.

The 8500 GT's leading performance here is likely due to a combination of factors. Newer drivers, a unified shader architecture that lines up better with what the benchmark is optimized to run on, etc... It's still remarkable how well the iPad 4's A6X SoC does here as well as Qualcomm's Snapdragon 600/Adreno 320. The latter is even more impressive given that it's constrained to the power envelope of a large smartphone and not a tablet. The fact that we're this close with such portable hardware is seriously amazing.

At the end of the day I'd say it's safe to assume the current crop of high-end ultra mobile devices can deliver GPU performance similar to that of mid to high-end GPUs from 2006. The caveat there is that we have to be talking about performance in workloads that don't have the same memory bandwidth demands as the games from that same era. While compute power has definitely kept up (as has memory capacity), memory bandwidth is no where near as good as it was on even low end to mainstream cards from that time period. For these ultra mobile devices to really shine as gaming devices, it will take a combination of further increasing compute as well as significantly enhancing memory bandwidth. Apple (and now companies like Samsung as well) has been steadily increasing memory bandwidth on its mobile SoCs for the past few generations, but it will need to do more. I suspect the mobile SoC vendors will take a page from the console folks and/or Intel and begin looking at embedded/stacked DRAM options over the coming years to address this problem.

 

Choosing a Testbed CPU & 3DMark Performance
Comments Locked

128 Comments

View All Comments

  • lmcd - Thursday, April 4, 2013 - link

    if the C-50 is about equal to the Z-2760, + 15% IPC + die shrink suddenly AMD is in this, so I'd say you didn't factor it in very well then...
  • whyso - Friday, April 5, 2013 - link

    The asus vivotab smart is pretty much rock bottom in these tests. using the z2760.
  • kyuu - Thursday, April 4, 2013 - link

    No, it's not. The E-350 is actually still stronger than the A15s. The only reason those ARM SoCs get a better score in the physics test is because they are quad-core compared to the E-350's two cores. Also, as ET stated below, performance doesn't scale down linearly with power, so a Bobcat at, say, a 75% lower TDP isn't going to have 75% lower performance. Heck, you can look at 3DMark results for the C-60 to see that it still outperforms the ARM SoCs at a lower TDP (assuming nothing fishy is going on with those results). The Z-60, with a 4.5W TDP, should still have comparable performance to the C-60.

    Plus, Bobcat is a couple years old. When AMD (finally) gets Jaguar out sometime this year, it should handily beat any A15-based SoC.

    Finally, if this shows that AMD is "bad", then it would show Intel as "absolutely pathetic".
  • Wilco1 - Thursday, April 4, 2013 - link

    E-350 certainly looks good indeed, however I would expect that A15 and E-350 will be close in most single threaded benchmarks, especially considering the latest SoCs will have higher frequencies (eg. Tegra 4 is 1.9GHz). On multi-threaded E-350 will lose out against any quad-core as the physics results show.

    A Z-60 at 1GHz will be considerably slower than an E-350 at 1.6GHz, so will lose out against pretty much all A15 SoCs. How well Jaguar will do obviously depends on the IPC improvement and clock speeds. But unless it is quad core, it certainly won't win all benchmarks.
  • Spunjji - Friday, April 5, 2013 - link

    Kabini uses 4 jaguar cores, Temash uses a pair of them. 15% IPC improvement combined with a clock speed bump from the die shrink should see it easily reaching competitive levels with the corresponding A15-based SoCs.
  • milli - Thursday, April 4, 2013 - link

    You're looking at it the wrong way. The E-350 is a desktop/netbook cpu. If you want to make a direct comparison, you should compare it to the C-60. That one is 9W (compared to an estimated 5W for the A6X). It will still beat the A6X on CPU performance and stay close enough in 3D. It's still produced on 40nm (compared to A6's 32nm) and has a much smaller die (75mm² vs 123mm²). AMD 64-bit memory interface, A6X 128-bit. If you look at it that way, AMD isn't doing too bad.
    Jaguar/GCN based Temash will be able to get C-60 performance or better under 4W.
  • lmcd - Thursday, April 4, 2013 - link

    The die size is what really gets me. AMD should be able to push Temash everywhere if they hit the die shrink advantages, push the GPU size up a bit and Jaguar core delivers.
  • jabber - Thursday, April 4, 2013 - link

    Interesting article. I'm always intrigued to know how far we've come.

    I think what would be really handy is an annual "How things have progressed!" round up at the end of the year.

    This would entail picking up all the generations past and present top of the range flagship cards (excluding the custom limited edition bizzaro models) and doing a range of core benchmarks. You could go back as far as the first PCI-e cards (2004 ish).

    Up until a few years ago I was still running a 7900GTX but really have no clue as to how much better current cards are in real hard facts and figures.

    Would be good to see how far we have been progressing over the past 10 years.
  • marc1000 - Thursday, April 4, 2013 - link

    I too would like to see an actual gaming comparison on GPUs from 2004 to now. Even if just on a small number of games, and with limited IQ settings.

    Something like testing 3 games: 1 real light, 1 console port, and 1 current and heavy. All benchmarked at medium settings, on 1280x720 or 1680x1050 resolution. no need to scale IQ, AA settings or triple-monitor situations.

    (pick just DX9 games if needed, most people who are NOT tech enthusiasts can't tell the difference between DX9 and DX11 anyway.)
  • dj christian - Thursday, April 4, 2013 - link

    +1 to that!

Log in

Don't have an account? Sign up now