Alpha version of Benchmark, was: GUI example anyone?

[EgonOlsen]

Uploaded the current version to the market. Search for "3d benchmark" or just "jpct".

[EgonOlsen]

Here are some results from a Nexus One @ 2.1:

Nexus one results (533*320)
Fillrate ST/MT: 6.70/5.43 MP/sec.
High object count: 15.76 fps
Multiple lights: 41.63 fps
High polygon count: 22.13 fps
Keyframe animation: 45.43 fps
Game level: 25.05 fps
Total Score: 4065

and again the 2.2 scores from dl.zerocool:

Nexus one results (533*320)
Fillrate ST/MT: 10.12/10.04 MP/sec.
High object count: 19.14 fps
Multiple lights: 51.08 fps
High polygon count: 23.03 fps
Keyframe animation: 60.47 fps
Game level: 24.71 fps
Total Score: 4856

Fillrate is pretty low. That's an effect that my phone shows too from time to time, which is why these tests are not part of the total score. Ignoring that, the scores are still lower...however, the increase by the jit is not very large, which shows that even the non-jited phones are more gpu than cpu limited in these tests.

More scores can be found here: http://androidforum.cz/viewtopic.php?f=6&t=5052. The forum in a czech one, but numbers are international and google's translator does a pretty good job on it.

BTW: Why is the resolution so strange? I thought that the N1 can do 800*480?

[EgonOlsen]

Updated it again, it has a little title screen and some options menu now (where you can select texture bpp and VBO usage).

A question to all Nexus One people (i.e. dl.zerocool...   ): If i understand it correctly, the 800*480 resolution of the screen refers to the display's subpixels, not to the framebuffer resolution which might explain why i'm getting 533*320 reported as physical resolution. To confirm this, i have a question: Does the benchmark fill the whole screen on the N1?

[zammbi]

Confused on the options. Is what's showing the current setting or if pressed that's what setting it will change too?

16bit, vbo off (as shown in the settings)

Milestone(2.1) results (569*320)

Fillrate ST/MT: 10.09/8.37 MP/sec.
High object count: 15.3 fps
Multiple lights: 41.13 fps
High polygon count: 15.01 fps
Keyframe animation: 58.58 fps
Game level: 24.64 fps
Total Score: 4319

32bit, vbo on(as shown in the settings)

Milestone(2.1) results (569*320)

Fillrate ST/MT: 10.44/8.73 MP/sec.
High object count: 14.23 fps
Multiple lights: 40.50 fps
High polygon count: 21.64 fps
Keyframe animation: 57.48 fps
Game level: 29.86 fps
Total Score: 4556

[EgonOlsen]

Confused on the options. Is what's showing the current setting or if pressed that's what setting it will change too?

I know...i always have that kind of problem myself with GUIs of that kind. I tried to make it clearer that it shows the current settings by using the : ...obviously, this wasn't 100% successful.

Your results are pretty interesting as they show that using VBOs on the Milestone improves performance. On my phone, this isn't the case. With or without VBO is all the same on the Galaxy.

[zammbi]

Your results are pretty interesting as they show that using VBOs on the Milestone improves performance. On my phone, this isn't the case. With or without VBO is all the same on the Galaxy.

Ah. And here's the results for 16bit /VBOs on:

Milestone(2.1) results (569*320)

Fillrate ST/MT: 10.46/10.29 MP/sec.
High object count: 15.28 fps
Multiple lights: 42.54 fps
High polygon count: 21.81 fps
Keyframe animation: 61.37 fps
Game level: 32.47 fps
Total Score: 4846

Nice improvement.

A question to all Nexus One people (i.e. dl.zerocool...   ): If i understand it correctly, the 800*480 resolution of the screen refers to the display's subpixels, not to the framebuffer resolution which might explain why i'm getting 533*320 reported as physical resolution. To confirm this, i have a question: Does the benchmark fill the whole screen on the N1?

My screen is 854x480. But reports it as 569*320. Its filled the whole screen.

[EgonOlsen]

My screen is 854x480. But reports it as 569*320. Its filled the whole screen.

Those resolutions seem to be kinda fake on modern phones as they don't seem to reflect real framebuffer size  of the hardware but the display's (sub-)pixel resolution (http://www.boygeniusreport.com/2010/03/26/google-nexus-one-display-actually-not-800x480-resolution/)...or it there a way to change the resolution that the Activity is using?

[zammbi]

Hope this helps: http://forum.xda-developers.com/showthread.php?t=614849

[EgonOlsen]

Kind of...but i'm still not sure if it's really using 569*320 and scales up or if it just reports that resolution to 1.5 based apps (which don't know of different resolutions AFAIK) and uses another resolution internally. Most likely it's the former, because otherwise, no older app with fixed size assets would work properly.

[zammbi]

I think you need to use 1.6 or higher.

[raft]

Nexus One Stock (2.1) results

Fillrate ST/MT: 7.43/6.69 MP/sec.
High object count: 15.88 fps
Multiple lights: 42.12 fps
High polygon count: 22.02 fps
Keyframe animation: 45.65 fps
Game level: 23.68 fps

Total Score: 4037

[EgonOlsen]

A N1...coooool. Can you please post a screen shot from the benchmark!? Maybe the high object count scene? I would like to see if the reported resolution really is just a fake and the actual resolution is that of the physical screen (like the docs state...but they don't talk about OpenGL, so i want to be sure).

[raft]

A N1...coooool.

sure here it's:


seems as it's 800x480. i would post resolution but couldn't find it. jPCT doesn't log it either.

btw, speaking of the log, you may want to log benchmark results so allow us to copy paste

[EgonOlsen]

Ok, it's 800*480, but it looks upsampled to me. So we are in the happy situation that some phones that support higher resolutions (like the N1) use a lower resolution when running an 1.5 based app than the physical one, while others (Dell Streak, Archos 5) are reporting and using their native or at least close to native resolutions (http://www.chazclout.co.uk/?tag=an3dbench) despite what the docs say...just great!

The docs (http://developer.android.com/guide/practices/screens_support.html) state that Android 1.6+ is supposed to "lie" to the 1.5 based apps about the real resolution and report a resolution that is close to what 1.5 supports and rescales internally. Obviously, that's not true for OpenGL...that wouldn't be too bad, if they would behave in a consistent manner...

[raft]

The docs (http://developer.android.com/guide/practices/screens_support.html) state that Android 1.6+ is supposed to "lie" to the 1.5 based apps about the real resolution and report a resolution that is close to what 1.5 supports and rescales internally. Obviously, that's not true for OpenGL...

that's true at least for N1. reported resolution is 533x320 and screen is definetely scaled. my 192 pixel wide blitted buttons seem ~290 pixel wide.
or are you saying something else ?