GLBenchmark 2.1 Solves Our Resolution Problems

Modern Android smartphones either run at 800 x 480 (WVGA) or 960 x 540 (qHD). The iPhone 4 features a 960 x 640 (DVGA) display, while the iPad 2 has a 1024 x 768 (XGA) panel. To complete the confusion Honeycomb tablets run at 1280 x 800 (WXGA). While measuring 3D performance at native resolution is useful in determining how well games will run on a device, it's not particularly useful in comparing GPUs. Fill rate and memory bandwidth requirements increase with pixel count. Even just between Android devices, those with a qHD display have 35% more pixels to render than their WVGA counterparts.

Unfortunately not all benchmarks give us the ability to perform tests at a common resolution. To make matters worse, not all devices are even capable of running at the resolutions we'd want to test. BaseMark ES2, the rebranded 3DMarkMobile allows us to specify display resolution which we have done in previous reviews. For smartphones we standardize on 640 x 480 and for tablets it's 1024 x 768. GLBenchmark however hasn't given us the ability to do that until recently.

GLBenchmark 2.1 now includes the ability to render the test offscreen at a resolution of 1280 x 720. This is not as desirable as being able to set custom resolutions since it's a bit too high for smartphones but it's better than nothing. The content remains unchanged from GLBench 2.0, there are still two primary tests that measure overall OpenGL ES 1.0 and 2.0 performance in addition to a number of specific synthetic feature tests.

We'll start with some low level tests to give us an idea of what we're looking at. First up is a raw triangle throughput test:

Triangle Throughput - GLBenchmark 2.1 Triangle Test

GLBenchmark 2.1 made some changes to the fill rate and triangle throughput tests so these numbers aren't comparable to the 2.0 results. Although the Nexus S' single core CPU, older drivers and lower clocked GPU put it at the bottom of the list, the LG Optimus 3D is the best showing of the PowerVR SGX 540. The SGX 540 in the LG phone ends up at around half the peak triangle rate of the iPad 2, perhaps due to better drivers or a higher clock speed. Here we see the true limitations of ARM's 4:1 pixel to vertex shader architecture. The Mali-400 barely outperforms the Nexus S and offers around 1/3 of the triangle rate of the PowerVR SGX 540 in the Optimus 3D. The Adreno 220 does well here and ends up at around 2x the performance of the Mali-400.

Triangle Throughput - GLBenchmark 2.1 Textured, Vertex Lit Triangle Test

As we move to a more complex triangle test the PowerVR SGX 540 in the Optimus 3D is now only 85% faster than the Mali-400. The Nexus S' performance, despite using the same GPU, is simply abysmal. The Adreno 220 drops to only 37% faster than the Mali-400. No matter how you slice it, the 4-core Mali-400 just can't compete in geometry performance with today's GPUs. Luckily for ARM however, most mobile games aren't geometry bound - what we really need here is pixel processing power and that's something Mali-400 does deliver quite well.

Fill Rate - GLBenchmark 2.1 Texture Fetch

GLBenchmark 2.1's fill test paints a different picture for Mali-400. Here the SGX 540 is less than half the speed while the iPad 2's SGX 543MP2 is about twice the speed. The Mali-400's texturing performance is very solid, no GPU currently shipping in a smartphone can touch it.

What about in a game-like workload? For that we turn to the standard GLBenchmark game tests: Egypt and Pro.

GLBenchmark 2.1—as its name implies—tests OpenGL ES 2.0 performance on compatible devices. The suite includes two long benchmarking scenarios with a demanding combination of OpenGL ES 2.0 effects - texture based and direct lighting, bump, environment, and radiance mapping, soft shadows, vertex shader based skinning, level of detail support, multi-pass deferred rendering, noise textures, and ETC1 texture compression.

GLBenchmark 2.1 is the best example of an even remotely current 3D game running on this class of hardware—and even then this is a stretch. If you want an idea of how the Mali-400 stacks up to the competition however, GLBenchmark 2.1 is probably going to be our best bet (at least until we get Epic to finally release an Unreal Engine benchmark).

First let's look at the 1280 x 720 results from 2.1:

GLBenchmark 2.1 - Egypt - Offscreen

GLBenchmark 2.1 - Pro - Offscreen

Despite huge disadvantages in geometry performance the Mali-400 does extremely well in the Egypt test, outpacing most of its competitors by a factor of 2. Only the iPad 2 is faster but that's to be expected based on the raw horsepower of its GPU. Given current workloads, ARM's Mali-400 is clearly the fastest GPU available on a smartphone today.

RightWare Basemark ES 2.0 V1 - Taiji

RightWare Basemark ES 2.0 V1 - Hoverjet

The dominance continues in the Basemark ES 2.0 tests, the Galaxy S II consistently delivers frame rates more than 2x those of its competitors. It's a shame that 3D gaming isn't a bigger deal on Android today because it'd be nice to really see ARM's high end GPU get a chance to flex its muscle on a regular basis.

For comparison to our older phones we've got our standard GLBenchmark 2.0 graphs below:

GLBenchmark 2.0 - Egypt

GLBenchmark 2.0 - PRO

Scrolling Performance

The Galaxy S II is by far the smoothest scrolling Android device we've ever reviewed. Architecturally it has all of the right components to deliver a buttery smooth UI: gobs of memory bandwidth and a very high speed GPU. The software appears to complement it very well. Once again we turn to Qualcomm's Vellamo benchmark to quantify scrolling performance on the Galaxy S II:

Qualcomm Vellamo Benchmark - Scrolling Performance Tests
WVGA Unless Otherwise Noted Ocean Flinger Image Flinger Text Flinger
HTC EVO 3D (Adreno 220 - qHD) 68.98 26.03 41.79
Motorola Photon 4G (GeForce ULP) 62.07 17.64 35.21
Samsung Galaxy S 4G (PowerVR SGX 540) 55.98 26.27 31.83
Samsung Galaxy S 2 (Mali-400 MP4) 91.02 35.14 51.19

Vellamo produces its scores directly from frame counters, so what you're looking at is a direct representation of how fast these devices scroll through the three web tests above. The Galaxy S II is 20 - 35% faster than the Photon 4G and 45 - 100% faster than the EVO 3D. We simply have no complaints here.

Flash Performance

Thus far NVIDIA's Tegra 2 has delivered the best overall GPU accelerated Flash expierence of any SoC on the market today. With the latest update to Flash enabling NEON support on OMAP 4 both it and the Exynos 4210 now match what NVIDIA delivers here:

Flash Performance

Until we hit 2012 and meet NVIDIA's Kal-El in smartphones (tablet release in 2011) and Qualcomm's first Krait designs, Samsung's Exynos 4210 looks like the best SoC for Android smartphones.

 

The Mali-400 Battery Life and Conclusions
POST A COMMENT

132 Comments

View All Comments

  • VivekGowri - Sunday, September 11, 2011 - link

    I literally cannot wait to read this article, and I similarly cannot wait for SGS2 to launch in the US. Reply
  • ImSpartacus - Sunday, September 11, 2011 - link

    You guys don't get early access to drafts? Reply
  • niva - Monday, September 12, 2011 - link

    I own an original Galaxy S, until it's been proven that Samsung updates to the latest Android within a month after major releases I will not buy anything but a Nexus phone in the future (assuming I even go with Android). By the time that decision has to be made I'm optimistic there will be unlocked WP7 Nokias available. Reply
  • Havor - Monday, September 12, 2011 - link

    Seriously , whats the problem, I was running 2.2 and 2.3 when they came out, could have them sooner, I just dont like to run roms with beta builds.

    So you never heard of Rooting and Custom Roms?

    Its the nature of companies to have long and COSTLY eternal testing routs, done mainly by people with 9 to 5 jobs, as delivering buggy roms is bad for there name, but then so is not updating to but its lots less hurtful, as most people dont care or know any better.

    Next to that if your phone is a phone is customized with extra crapeware by your provider it can be that it takes months before you get a update even do Samsung delivered one a long time ago.

    The rooting scene is totally different, its done by nerds with passion for what they do, and yes the early/daily builds have bugs but also get mouths quicker reported and fixed by the scene.
    And imho are the final updates just as stable as the factory builds.

    Dont like how your Android is working?
    Stop bitching and fixed your self, its not that hard, as it is a OS platform, just make sure you can root your phone, before you buy it.

    The following website explains it all.
    http://androidforums.com/galaxy-s-all-things-root/...
    http://androidforums.com/galaxy-s-all-things-root/
    Reply
  • vision33r - Monday, September 12, 2011 - link

    If it's your personal phone, you can do whatever you want. However like some of us here with jobs that let us pick phones. One requirement is the phone has to be stock and no rooting allowed.

    Samsung is about the worst of the 3 makers in terms of software updates.
    Reply
  • niva - Monday, September 12, 2011 - link

    Seriously calm down, I've heard plenty about rooting and custom roms but phone hackery is not something I'm interested in right now. I don't have the time or energy for it. I shouldn't have to manually go through rooting and updating my phone, especially when security issues are involved.

    I like the way 2.2 is working on the SGS. I bought this phone from a friend who upgraded and it's not something I would've paid the retail price for. I've not run into anything so far that's made me actually bother with the rooting and manual upgrade process. I've not read into rooting the phone or updating it, but I'm sure if I get into it this will take me a long time (hours/days) which I shouldn't need to sacrifice to run the latest version of the OS.

    From the political standpoint the blame is both on Samsung and T-Mobile apparently in terms of getting the new revisions out.

    From my personal standpoint I despise all companies who do not use the default Android distro, running skins and secondary apps, on the phones they ship out. While some of the things they do are nice, it slows down their ability to keep up with android revisions.

    On the other hand, my wife's Nexus (original one) updates faster than internet posts saying Android 2.3.x has been rolled out. It's friggin awesome. She had one problem with battery draining really fast after a recent upgrade but I managed to fix that after a couple of hours of forum searching and trying different things.

    So it's simple, if I will buy another Android in the future, it will be a Nexus phone, where I know from personal experience that everything works in terms of having the latest and greatest. Notice the Nexus S is made by Samsung, it's for the most part identical to the phone I have, yet gets the updates immediately and doesn't have the known security problems I'm exposed to.
    Reply
  • ssj4Gogeta - Monday, September 12, 2011 - link

    Well, the international version got 2.3.3 around ~3 months ago here (and earlier for other countries). Reply
  • poohbear - Tuesday, September 13, 2011 - link

    vision33r u dont know what you're talking about. People bitch and complaina bout software updates, but how are the quality of those updates? when its updated too soon there are bugs and ppl complain, updated later ppl complain about the wait times. I remember last year Motorola said they're not updating their XT720 to android 2.2., they're leaving it at 2.1. S korea Motorola was the only branch that decided to do it, but guess what? 2.2 was too much for the hardware in the XT720 to handle, and it ran slooooow! XT720 users all over complained about it, but the reality is the phone couldnt handle it. 90% of smartphone users want something stable that works, they dont care about having the latest and greatest Android build. So if Samsung errs on the side of quality and takes more time to release stable quality software, then all the power to them! Reply
  • anishannayya - Friday, September 23, 2011 - link

    Actually, if updates are your hard-on, then you'd likely be looking at Motorola in the future (due to the Google acquisition).

    The entire reason why the Nexus lines of phones are quick to get updates is because the are co-developed with Google. As a result, these phones are the ones the Google developers are using to test the OS. When it is ready to go, it is bug free on the device, so Samsung/HTC can roll it out immediately.

    At the end of the day, any locked phone is plagued by carrier bloatware, which is the biggest slowdown in software release. Just buy an unlocked phone, like this one, in the future.
    Reply
  • ph00ny - Sunday, September 11, 2011 - link

    It's awesome to see this article finally
    I'm glad François Simond aka supercurio contributed to the article

    Btw that slot on the left is for the hand strap which is very popular in asia for accessory attachments
    Reply

Log in

Don't have an account? Sign up now