www.jpct.net
jPCT-AE - a 3d engine for Android => Projects => Topic started by: EgonOlsen on May 25, 2010, 11:36:10 pm
-
Looks like it. I'll try that later. For now, my Broadcast-stuff works fine. Here's an early alpha of the benchmark...it runs once and exits after displaying the results. I would be interested in some results: http://www.jpct.net/jpct-ae/download/alpha/bench/Benchmark-AE.apk (http://www.jpct.net/jpct-ae/download/alpha/bench/Benchmark-AE.apk)
-
Hi, Here are some results, ps : If you have new version of JPCT I would like to try them because Tuesday we have to
give our application to our teacher, it's the dead line. :P
I'll publish what we have done, in the forum at the same time, but I'm too busy at moment to deliver a stable version.
Nexus one : Froyo 2.2 Results : (1st test)
Fillrate ST/MT : 10.05/9.14 Megapixel/sec
High object count: 18.24 fps
Multiple lights: 45.05 fps
High polygon count: 22.60 fps
(I really like the high poly and multiple light test ;) )
(2nd test)
Fillrate ST/MT : 10.11/9.11 Megapixel/sec
High object count: 17.94 fps
Multiple lights: 45.37 fps
High polygon count: 22.43 fps
Results are pretty stable
-
Motorola Milestone stock- Android 2.1:
Fillrate ST/MT : 9.18/8.37 Megapixel/sec
High object count: 13.92 fps
Multiple lights: 39.98 fps
High polygon count: 14.91 fps
-
Something to laugh at:
Samsung Galaxy i7500, Android 1.5:
Fillrate ST/MT : 7.97/7.47 Megapixel/sec (fluctuates, sometimes its down to 4.5...)
High object count: 7.88 fps
Multiple lights: 24.19 fps
High polygon count: 4.68 fps
-
Restarted the Phone:
Fillrate ST/MT : 10.67/9.86 Megapixel/sec
High object count: 15.45 fps
Multiple lights: 41.65 fps
High polygon count: 15.16 fps
Then exited most applications running:
Fillrate ST/MT : 10.77/10.39 Megapixel/sec
High object count: 15.61 fps
Multiple lights: 41.80 fps
High polygon count: 15.40 fps
-
Hi, Here are some results, ps : If you have new version of JPCT I would like to try them because Tuesday we have to
give our application to our teacher, it's the dead line. :P
Not much has changed from the last uploaded version. It's not really worth an update so far.
-
Okay,
Thank you so I'll keep my current jpct.
I've a looooooooooooooooooooooooot to do !
Rush time XD
-
Updated the benchmark with a version that includes an additional test (game level). My phone renders 6.5 fps in that test... :(
-
The last test looks like a quake map :P
I forget to say last time, on spica high poly make the phone totally freeze on loading, had to remove battery.
Nexus Results of new version :
Results(533*320)
ST/MT : 10.02/10.29 Mp/sec
High object count: 18.70fps
Multiple lights: 51.70fps
High polygon count: 23.43fps
Game level: 24.83fps
-
Not much i can do about that spica problem. I think the high polygon load just killed the phones software renderer. I will try it in the emulator to see, if it kills that renderer too. I once tried it, but i can't remember the outcome.
-
Game level for me was 24.25 fps.
-
I've updated the apk again. It now includes the compile time improvements of the new version of AE, an additional test (animations) and a total score. The score is calculated so that my Galaxy scores around 2000 (to make me feel better... ;D ).
Now all the tests are in their final form (for now). I may add some web access to store the results on a server later.
About the Spica problem: No idea...the test works fine in the emulator (albeit with false lighting, but that was to be expected), so it has to be a problem with that particular phone. Do you have access to the log?
-
Fillrate ST/MT : 10.47/10.48 Megapixel/sec
High object count: 15.38 fps
Multiple lights: 42.20 fps
High polygon count: 15.29 fps
Keyframe animation: 61.51 fps
Game level: 24.59 fps
Total score: 4452
-
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
(About the spica, I don't have access to it right now I'll try again Monday when I'll have again access to spica)
-
Updated the benchmark. Results should not change at all, but it uses less memory now.
-
Uploaded the current version to the market. Search for "3d benchmark" or just "jpct".
-
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 (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?
-
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?
-
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
-
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.
-
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.
-
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/ (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?
-
Hope this helps: http://forum.xda-developers.com/showthread.php?t=614849
-
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.
-
I think you need to use 1.6 or higher.
-
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
-
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).
-
A N1...coooool.
;D
sure here it's:
(http://img36.imageshack.us/img36/8418/highobjectcount.png)
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 ;)
-
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 (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 (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... :P
-
The docs (http://developer.android.com/guide/practices/screens_support.html (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 ?
-
Samsung Galaxy S with Froyo comes close to 10000 (9996)...impressive...
-
Results on my Droid X:
Fillrate ST/MT: 10.99/11.07 MP/ sec.
High object count: 27.59fps
Multiple lights: 60.64 fps
High polygon count: 25.67 fps
Keyframe animationL 60.66 fps
Game level: 45.05 fps
TOTAL SCORE: 6015
-
Results on Xperia X10 (Japanese model)
VBO:On
Textures: 32bit
Fillrate ST/MT: 5.72/5.69 MP/ sec.
High object count: 16.78fps
Multiple lights: 31.51 fps
High polygon count: 29.78 fps
Keyframe animationL 31.49 fps
Game level: 31.35 fps
TOTAL SCORE: 3786
Depressing. Hope the upgrade to 2.1 later this year will change these results.
-
It's not depressing....I would be more than happy if my phone would come even close to these results... ;)
-
G1 with Froyo: ~1400 points
(http://img580.imageshack.us/img580/9534/devicee.png)
-
I downloaded the latest from the market.
Im using a Milestone 2.1, with beta JIT, and overclocked to 800(though It doesn't seem to be staying at that speed when running the test). One day I hope to get 2.2 (Next year for the Milestone)
It doesn't show the resolution any more, so I'm guessing its using my full 854x480?
16bit/VBO off:
Fillrate ST/MT: 10.35/9.54 MP/sec.
High object count: 21.25 fps
Multiple lights: 43.90 fps
High polygon count: 15.44 fps
Keyframe animation: 61.39 fps
Game level: 25.16 fps
Total Score: 4661
16bit/VBO on:
Fillrate ST/MT: 10.23/9.60 MP/sec.
High object count: 20.95 fps
Multiple lights: 43.27 fps
High polygon count: 21.88 fps
Keyframe animation: 61.47 fps
Game level: 32.85 fps
Total Score: 5008
-
Fillrate ST/MT 9.56/9.57 MP/sec.
High object count: 37.21 fps
Multiple lights: 55.61 fps
High polygon count: 45.39 fps
Keyframe animation: 55.70fps
Game level: 55.75 fps
TOTAL SCORE: 6760
On a SGS
-
Fillrate ST/MT 9.23/9.30 MP/sec.
High object count: 9.61 fps
Multiple lights: 62.93 fps
High polygon count: 40.67 fps
Keyframe animation: 61.71 fps
Game level: 38.38 fps
TOTAL SCORE: 5692
on LG Optimus One with Froyo
-
32bit/VBO on and same as 16bit/VBO off
Fillrate ST/MT 21.45/21.46 MP/sec.
High object count: 43.46 fps
Multiple lights: 55.90 fps
High polygon count: 55.28 fps
Keyframe animation: 55.73 fps
Game level: 55.73 fps
TOTAL SCORE: 7133
on SGS with Froyo beta
-
will be some new version for more powerful devices like as SGS, DHD, G2,... ?
-
Maybe yes. Any suggestions are welcome.
-
Maybe some large game level with a lot of lights and animated objects...
-
Problem with that is art work. Somebody has to do it (and that won't be me...lack of talent...) or it has to be freely available. I thought about doing a terrain rendering test, because terrains can be created in good quality pretty simple.
-
Or you can add sphere with this (http://www.oera.net/How2/PlanetTexs/EarthMap_2500x1250.jpg) texture and gradually add more and more polygons, until framerate drops to 25FPS :) ... or some realtime modify (VertexController) surface of plane, maybe flag or water efect :)
-
15965 on Nexus One with 2.3.3.
Total score: 15965
Double dragon: 11.86 fps
Flower power: 16.59 fps
Ninjas' garden: 10.68 fps
Emperor's new clothes: 37.35 fps
Magic island: 15.72 fps
btw, i really liked the look and feel of 2.3