For the past several days I've been playing around with Futuremark's new 3DMark for Android, as well as Kishonti's GL and DXBenchmark 2.7. All of these tests are scheduled to be available on Android, iOS, Windows RT and Windows 8 - giving us the beginning of a very wonderful thing: a set of benchmarks that allow us to roughly compare mobile hardware across (virtually) all OSes. The computing world is headed for convergence in a major way, and with benchmarks like these we'll be able to better track everyone's progress as the high performance folks go low power, and the low power folks aim for higher performance.

The previous two articles I did on the topic were really focused on comparing smartphones to smartphones, and tablets to tablets. What we've been lacking however has been perspective. On the CPU side we've known how fast Atom was for quite a while. Back in 2008 I concluded that a 1.6GHz single core Atom processor delivered performance similar to that of a 1.2GHz Pentium M, or a mainstream Centrino notebook from 2003. Higher clock speeds and a second core would likely push that performance forward by another year or two at most. Given that most of the ARM based CPU competitors tend to be a bit slower than Atom, you could estimate that any of the current crop of smartphones delivers CPU performance somewhere in the range of a notebook from 2003 - 2005. Not bad. But what about graphics performance?

To find out, I went through my parts closet in search of GPUs from a similar time period. I needed hardware that supported PCIe (to make testbed construction easier), and I needed GPUs that supported DirectX 9, which had me starting at 2004. I don't always keep everything I've ever tested, but I try to keep parts of potential value to future comparisons. Rest assured that back in 2004 - 2007, I didn't think I'd be using these GPUs to put smartphone performance in perspective.

Here's what I dug up:

The Lineup (Configurations as Tested)
  Release Year Pixel Shaders Vertex Shaders Core Clock Memory Data Rate Memory Bus Width Memory Size
NVIDIA GeForce 8500 GT 2007 16 (unified) 520MHz (1040MHz shader clock) 1.4GHz 128-bit 256MB DDR3
NVIDIA GeForce 7900 GTX 2006 24 8 650MHz 1.6GHz 256-bit 512MB DDR3
NVIDIA GeForce 7900 GS 2006 20 7 480MHz 1.4GHz 256-bit 256MB DDR3
NVIDIA GeForce 7800 GT 2005 20 7 400MHz 1GHz 256-bit 256MB DDR3
NVIDIA GeForce 6600 2004 8 3 300MHz 500MHz 128-bit 256MB DDR

I wanted to toss in a GeForce 6600 GT, given just how awesome that card was back in 2004, but alas I had cleared out my old stock of PCIe 6600 GTs long ago. I had an AGP 6600 GT but that would ruin my ability to keep CPU performance in-line with Surface Pro, so I had to resort to a vanilla GeForce 6600. Both core clock and memory bandwidth suffered as a result, with the latter being cut in half from using slower DDR. The core clock on the base 6600 was only 300MHz compared to 500MHz for the GT. What does make the vanilla GeForce 6600 very interesting however is that it delivered similar performance to a very famous card: the Radeon 9700 Pro (chip codename: R300). The Radeon 9700 Pro also had 8 pixel pipes, but 4 vertex shader units, and ran at 325MHz. The 9700 Pro did have substantially higher memory bandwidth, but given the bandwidth-limited target market of our only cross-platform benchmarks we won't always see tons of memory bandwidth put to good use here.

The 7800 GT and 7900 GS/GTX were included to showcase the impacts of scaling up compute units and memory bandwidth, as the architectures aren't fundamentally all that different from the GeForce 6600 - they're just bigger and better. The 7800 GT in particular was exciting as it delivered performance competitive with the previous generation GeForce 6800 Ultra, but at a more attractive price point. Given that the 6800 Ultra was cream of the crop in 2004, the performance of the competitive 7800 GT will be important to look at.

Finally we have a mainstream part from NVIDIA's G8x family: the GeForce 8500 GT. Prior to G80 and its derivatives, NVIDIA used dedicated pixel and vertex shader hardware - similar to what it does today with its ultra mobile GPUs (Tegra 2 - 4). Starting with G80 (and eventually trickling down to G86, the basis of the 8500 GT), NVIDIA embraced a unified shader architecture with a single set of execution resources that could be used to run pixel or vertex shader programs. NVIDIA will make a similar transition in its Tegra lineup with Logan in 2014. The 8500 GT won't outperform the 7900 GTX in most gaming workloads, but it does give us a look at how NVIDIA's unified architecture deals with our two cross-platform benchmarks. Remember that both 3DMark and GL/DXBenchmark 2.7 were designed (mostly) to run on modern hardware. Although hardly modern, the 8500 GT does look a lot more like today's architectures than the G70 based cards.

You'll notice a distinct lack of ATI video cards here - that's not from a lack of trying. I dusted off an old X800 GT and an X1650 Pro, neither of which would complete the first graphics test in 3DMark or DXBenchmark's T-Rex HD test. Drivers seem to be at fault here. ATI dropped support for DX9-only GPUs long ago, the latest Catalyst available for these cards (10.2) was put out well before either benchmark was conceived. Unfortunately I don't have any AMD based ultraportables, but I did grab the old Brazos E-350. As a reminder, the E-350 was a 40nm APU that used two Bobcat cores and featured 80 GPU cores (Radeon HD 6310). While we won't see the E-350 in a tablet, a faster member of its lineage will find its way into tablets beginning this year.

Choosing a Testbed CPU & 3DMark Performance


View All Comments

  • jeffkibuule - Thursday, April 4, 2013 - link

    I'm not sure how much more significant overhead there is left when you remove APIs. At least with iOS, developers can specifically target performance characteristics of certain devices if they wish, only problem is that a graphically intense game isn't such an instant money maker on handhelds like it is on consoles. Almost no incentive to go down that route. Reply
  • SlyNine - Saturday, April 6, 2013 - link

    You have to remember that a 7900GT is faster than a 8500GT, hell the 8600GT had 2x as many shaders and that performed closely to the 8600GT.

    Even still I doubt that the benchmark does as well as it could on a 8500GT if it were better optimized. I'm willing to bet you're about right with the Geforce FX estimate.
  • whyso - Thursday, April 4, 2013 - link

    Is this showing how bad AMD is? E-350 is a 18 watt tdp. Even if they double perf/watt with jaguar you are still looking at a chip that hangs with an ipad 4 at 9 watts. Reply
  • tipoo - Thursday, April 4, 2013 - link

    The 3DMark online scores seem to be showing higher numbers for the E350, but perhaps those pair it with fast RAM, since RAM seems to be the bottleneck on AMD APUs. Reply
  • Flunk - Thursday, April 4, 2013 - link

    A lot of people overclock their equipment for 3Dmark. Reply
  • oaso2000 - Thursday, April 4, 2013 - link

    I use a E350 as my desktop computer, and I get much higher results than those in the article. I don't overclock it, but I use 1333 MHz RAM. Reply
  • ET - Thursday, April 4, 2013 - link

    You're assuming that performance is linear with power and that a PC processor has the same power as a tablet processor. It's enough to take a look at the other Brazos processors to see that's not the case.

    The C-50 runs at a lower clock speed of 1GHz vs. 1.6GHz but is 9W. The newer C-60 adds boosting to 1.33GHz.

    The Z-60 is a mobile variant which runs at 1GHz and has a TDP of 4.5W.

    It's hard to predict where AMD's next gen will land on these charts, but it's obviously not as far in terms of performance/power as you peg it to be.

    For me, even if AMD does end up a little slower than some ARM CPU's, I'd pick such as Windows tablet over an ARM based tablet for its compatibility with my large library of (mostly not too demanding) games.
  • whyso - Thursday, April 4, 2013 - link

    The nexus 4 is already more powerful than the e-350 while consuming much less power. By the time jaguar launches, even if they double perf/watt they are still going to be behind any high end tablet or phone soc.
    c-50 is weaker or the same than atom z-2760 which does't do too well.
  • lmcd - Thursday, April 4, 2013 - link

    You both didn't factor the die shrink... This is 40nm. Reply
  • whyso - Thursday, April 4, 2013 - link

    yes I did, I'm assuming they can double perf/ watt to do that they will need to shrink the die. Jaguar only boost IPC by ~15% with small efficiency gains. By going down to 28 nm they might be able to double perf /watt (which is a clearly optimistic prediction). Reply

Log in

Don't have an account? Sign up now