We're constantly on the lookout for new benchmarks to use for benchmarking the latest SoCs in devices. Today, Kishonti Informatics released GLBenchmark 2.0, the latest version of its popular GLBenchmark suite for measuring 3D graphics performance across a host of platforms: iOS, Android, Symbian, Windows Mobile, and Maemo. We've been testing it out for a while now and have some numbers of our own and from the community results. The end result is yet another look at how 3D performance stacks up between nearly all modern SoCs.

GLBenchmark 2.0 - 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, and individual tests such as swap buffer speed (for determining the framerate cap), texture fill, triangle, and geometric tests. GLBenchmark 2.0 also leverages 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.

We've been testing devices for a little while now and have a decent enough spread to make for some interesting comparison. The only extra consideration is that all of these were run at the device's respective native resolution. There's no way to change resolution, and likewise numbers cannot be scaled linearly because we may be memory bandwidth limited on some devices. GLBenchmark will join our benchmark suite for devices going forward. 

First are the resolutions (native) of the devices themselves:

Device Resolutions - GLBenchmark Native Resolution
Google Nexus One 800x480 WVGA
LG Optimus One 320x480 HVGA
T-Mobile myTouch 4G 800x480 WVGA
Samsung Fascinate 800x480 WVGA
Google Nexus S 800x480 WVGA
HTC EVO 4G 800x480 WVGA
Apple iPhone 4 960x640 DVGA
Apple iPad 1024x768 XGA
Motorola Droid 854x480 FWVGA
T-Mobile G2 800x480 WVGA
Nokia N900 800x480 WVGA
Apple iPhone 3GS 320x480 HVGA

Thankfully, comparison across devices running Android is easy thanks to the relatively standard WVGA resolution guidelines for high end devices. 

GLBenchmark 2.0 - Egypt

GLBenchmark 2.0 - PRO

   The first benchmark, Egypt, tests OpenGL ES 2.0 and represents the newest and most demanding benchmark. The second -  GLBenchmark PRO - represents a suite that tests OpenGL ES 1.1 performance. (edit: GLBenchmark Pro also tests OpenGL ES 2.0 features, and is a port of an earlier GLBenchmark 1.1 test which focused on OpenGL ES 1.1 performance). Moving forward we will report these whenever possible on smartphone reviews. 

It's pretty apparent right now that PowerVR SGX 540 still holds the lead, though the new 45 nm Qualcomms with Adreno 205 are a huge jump forwards from Adreno 200 performance wise. It's interesting that it looks like we're GPU or memory bandwidth bound on those new Qualcomms, as evidenced by the similar results the myTouch 4G and G2 post despite a 200 MHz CPU clock disparity.

Overall, GLBenchmark is designed to showcase some of the OpenGL ES 2.0 features that developers may potentially use in future gaming titles. There are a lot more low level tests which we'll be playing around with in the future and using to test in much more detail. 

Comments Locked


View All Comments

  • NickDG - Friday, December 17, 2010 - link

    Can we see an OMAP3 SoC running at 1ghz? Droid X perhaps?

  • Brian Klug - Friday, December 17, 2010 - link

    I had to send ours back, but I'm trying to find one to include when we launch the smartphone bench. What I have now represents what I had on hand, but I'm equally interested in seeing Droid 2 or Droid X scores at 1 GHz. I'm trying to snag one. ;)

  • sarge78 - Friday, December 17, 2010 - link

    Just behind the new snapdragons.

    Egypt. 13fps

    Pro. 23fps

    (Motorola defy @ 1ghz)
  • sarge78 - Friday, December 17, 2010 - link

    The defy is running 2.1 btw (it shouldn't make a huge difference though?)
  • zorxd - Friday, December 17, 2010 - link

    Isn't this a 320x480 device? The Droid X/2 would also be interesting.
  • sarge78 - Friday, December 17, 2010 - link

    It's got the usual Motorola 854x480 FWVGA screen (essentially the same phone as droid 2/X etc)

    Just like the new Qualcomms they'll be SGX530 or memory bandwidth bound.
  • deputc26 - Friday, December 17, 2010 - link

    Good call, that's a fairly glaring omission.
  • probedb - Friday, December 17, 2010 - link

    Seriously? Is this right? Same GPU but the iPhone 4 has a faster CPU and yet it's slower?
  • Chloiber - Friday, December 17, 2010 - link

    Resolution and same GPU.
  • choirbass - Friday, December 17, 2010 - link


    3gs is .1536mp @ 320x480 600mhz
    most androids are .384mp @ 800x480 1ghz
    ip4 is .6144mp @ 960x640 850mhz
    ipad is .786432mp @ 1024x768 1ghz

    so the ip4 is driving 4x the resolution of ip3gs, most androids 2x and ipad just over 5x

    hopefully that should put the benchmarks more into perspective, because otherwise there is a huge unexplained disparity like was mentioned.

Log in

Don't have an account? Sign up now