Video of Froyo on Moto Droid

[jntdroid]

first video
- long bench: looked like around 880 average
- short bench: looked like around 410 average
- mflop: just above 10

second
- long: avg about 435
- short: avg about 185
- mflop: avg about 19

 

[Darkseider]

1.2ghz would b3 400 mhz faster the 800mhz.

Hope that's the answer you were looking for.

lol. i knew that, but what i was really asking is in reference to the speed tests in those 2 videos posted above my last post. how much faster are they compared to a droid running the same tests on 2.1( i know that 2.2 is supposed to be much faster than 2.1). and then how do they compare to a droid running running at 800mhz(i only ask that, because thats what my current set up, but i dont know how to do all of those tests because im an undereducated noob)

OK, then I'm not sure how to answer your question. You would have to actually run one against the other to find out I suppose. I don't know how one could tell you verbally in seconds and such how much faster that is.

Put it this way. If you were to root and overclock the Droid to 1.2 GHZ I doubt you would see any difference. Just an educated guess.

Actually the LinPack scales linearly based on clockspeed. It scores between .80 and .8115 MFlops per 100 Mhz. So a stock Droid at 550 Mhz will score approx. 4.4 to 4.5 MFlops EVERY time. A 1.2 Ghz Droid on 2.1 will score approx. 9.6 to 9.8 everytime.

 

[Darkseider]

OK so with those scores it not only proves that the LinPack does scale damned near perfectly linearly BUT also shows a 2x performance increase with Froyo. So based on that a stock Droid running Froyo should score 8.8 to 9.0 on the LinPack.

 

[squeak]

ok. i figured out how to run the tests in set cpu and here are the results from the videos vs my results:


2.2 stock from video: long bench mark scores - 1st attempt- 884ms 2nd- 876ms
Short bench mark scores - 1st attempt- 385ms 2nd- 450ms

2.2 1.2ghz from video: long - 1st 455ms 2nd 423ms
short - 1st 199ms 2nd 176ms

2.1 rooted 800mhz my phone: long - 1st 962ms 2nd 967ms
short - 1st 352ms 2nd 262ms




if anybody wants to add their scores for comparison with different speeds it would be interesting to see

 

[Darkseider]

ok. i figured out how to run the tests in set cpu and here are the results from the videos vs my results:


2.2 stock from video: long bench mark scores - 1st attempt- 884ms 2nd- 876ms
Short bench mark scores - 1st attempt- 385ms 2nd- 450ms

2.2 1.2ghz from video: long - 1st 455ms 2nd 423ms
short - 1st 199ms 2nd 176ms

2.1 rooted 800mhz my phone: long - 1st 962ms 2nd 967ms
short - 1st 352ms 2nd 262ms




if anybody wants to add their scores for comparison with different speeds it would be interesting to see

Download and run the Linpack as well. You should score between a 6.4 and 6.5

 

[squeak]

is it just in the market as 'linpack'?

 

[jntdroid]

I'm using Chevy's ULV 1ghz kernel, but turned it down to 550 max freq, 250 min. These are the average of 5 runs.

linpack: 4.3
short: 390
long: 1410 (any idea why this would be so high?)

 

[jntdroid]

n/m, just saw you are oc'd to 800

 

[jntdroid]

when fully oc'd to 1ghz - also, running stock root, no rom:

short: 189
long: 767
linpack: 8.1

 

[squeak]

linpack scores 800mhz rooted no rom- 5.339 5.408 5.136 4.989

 

[Rouger]

ok. i figured out how to run the tests in set cpu and here are the results from the videos vs my results:


2.2 stock from video: long bench mark scores - 1st attempt- 884ms 2nd- 876ms
Short bench mark scores - 1st attempt- 385ms 2nd- 450ms

2.2 1.2ghz from video: long - 1st 455ms 2nd 423ms
short - 1st 199ms 2nd 176ms

2.1 rooted 800mhz my phone: long - 1st 962ms 2nd 967ms
short - 1st 352ms 2nd 262ms




if anybody wants to add their scores for comparison with different speeds it would be interesting to see

You state you are using 2.2? How? Is this from the SDK or what?

 

[Darkseider]

I'm using Chevy's ULV 1ghz kernel, but turned it down to 550 max freq, 250 min. These are the average of 5 runs.

linpack: 4.3
short: 390
long: 1410 (any idea why this would be so high?)

Yup and the the LinPack is right in line as well. So I guess the question is how reliable is the Linpack benchmark if all it is doing is scaling linearly? With Froyo all it does is produce the same linear result as Android 2.1 x 2. So it does show that Froyo is doing something. The Incredible and Desire score a consistent 7.1 - 7.2 and a Nexus One at 1.13 Ghz scores a 7.75 so that shows .71 MFlops per 100 Mhz on a Snapdragon. From this we can infer that the OMAP 36xx series is more efficient at performing floating point calculations. It also proves that the linpack benchmark scales nearly perfectly with clockspeed based on processor.

So what does all this mean to me you and the guy next to you? Well other than comparing how well a SoC performs floating point operations compared to another SoC, nothing. There is still a bunch of other things like Integer ops, 2D/3D performance based on the GPU or lack thereof. Reads/Writes to main memory/SD Card and processor cache. So if nothing else it gives bragging rights to those of us who chose OMAP based devices. We can say we can do floating point math better than you! NYAH NYAH! but that's it.

 

[Rouger]

ok. i figured out how to run the tests in set cpu and here are the results from the videos vs my results:


2.2 stock from video: long bench mark scores - 1st attempt- 884ms 2nd- 876ms
Short bench mark scores - 1st attempt- 385ms 2nd- 450ms

2.2 1.2ghz from video: long - 1st 455ms 2nd 423ms
short - 1st 199ms 2nd 176ms

2.1 rooted 800mhz my phone: long - 1st 962ms 2nd 967ms
short - 1st 352ms 2nd 262ms




if anybody wants to add their scores for comparison with different speeds it would be interesting to see

You state you are using 2.2? How? Is this from the SDK or what?

Never mind I just figured out what you are showing. Guess I should read the post a few times before I comment next time :huh:

 

[squeak]

its all good man. we all make mistakes

 

[jntdroid]

I'm using Chevy's ULV 1ghz kernel, but turned it down to 550 max freq, 250 min. These are the average of 5 runs.

linpack: 4.3
short: 390
long: 1410 (any idea why this would be so high?)

Yup and the the LinPack is right in line as well. So I guess the question is how reliable is the Linpack benchmark if all it is doing is scaling linearly? With Froyo all it does is produce the same linear result as Android 2.1 x 2. So it does show that Froyo is doing something. The Incredible and Desire score a consistent 7.1 - 7.2 and a Nexus One at 1.13 Ghz scores a 7.75 so that shows .71 MFlops per 100 Mhz on a Snapdragon. From this we can infer that the OMAP 36xx series is more efficient at performing floating point calculations. It also proves that the linpack benchmark scales nearly perfectly with clockspeed based on processor.

So what does all this mean to me you and the guy next to you? Well other than comparing how well a SoC performs floating point operations compared to another SoC, nothing. There is still a bunch of other things like Integer ops, 2D/3D performance based on the GPU or lack thereof. Reads/Writes to main memory/SD Card and processor cache. So if nothing else it gives bragging rights to those of us who chose OMAP based devices. We can say we can do floating point math better than you! NYAH NYAH! but that's it.

you know a lot more than i do about all of that, but that's kinda the same conclusion i was getting to when looking at all of these numbers... plus (and fully I realize this is not the same as how froyo will be), when i've enabled JIT on my stock/non-oc'd phone, the linpack went up, but there was no noticeable difference in performance at all... the only thing that seemed to make a noticeable difference in actual phone usage (with the scores as well) was overclocking