Active Topics
-
HDMI with Leste (1)
to Maemo 7 / Leste by teroyk - 1 day, 16 hrs ago -
Firefox with Leste (9)
to Maemo 7 / Leste by teroyk - 3 days, 18 hrs ago - more...
 |
|
2009-11-04
, 23:05
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#33
|
Tear on N900 - starts at 40 and maxes at 88 when the bricks are out.
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
| The Following User Says Thank You to Bundyo For This Useful Post: | ||
|
|
2009-11-04
, 23:18
|
|
Posts: 183 |
Thanked: 18 times |
Joined on Jul 2009
@ italy
|
#34
|
so, I've redone the test, I will put some screenshots to show the stages of briks with the FPS average:
as you can see, the number of bricks seems to influence the FPS, but I have to admit that tear is fantastic...98 (and sometimes 100) is the score that My firefox 3.5.4 done on my dualcore x64 pc...
and it's arm11...
as you can see, the number of bricks seems to influence the FPS, but I have to admit that tear is fantastic...98 (and sometimes 100) is the score that My firefox 3.5.4 done on my dualcore x64 pc...
and it's arm11...
|
|
2009-11-04
, 23:21
|
|
Posts: 4,708 |
Thanked: 4,649 times |
Joined on Oct 2007
@ Bulgaria
|
#35
|
I fear that those benchmarks are of WebKit, not of Tear 
Also probably the X optimizations done by Serge are helping in N8x0, since in N900 its not so fast.
Also probably the X optimizations done by Serge are helping in N8x0, since in N900 its not so fast.
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.
|
|
2009-11-05
, 06:59
|
|
Posts: 177 |
Thanked: 128 times |
Joined on Jan 2008
@ Espoo, Finland
|
#36
|
I actually redid the test (for the HTC Hero), my original results were based on looking at it for something like 10 seconds. In the end, it maxes out at around 40, if I let it run. With the Steel browser, it's same in the beginning (10 or so) but goes up to 50.
Not sure what results we were supposed to report, but yes, it goes up quite a bit if you let it run.
Not sure what results we were supposed to report, but yes, it goes up quite a bit if you let it run.
 |
| Tags |
| performance javascript |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 11:40.
Last edited by ArnimS; 2009-11-04 at 22:38. Reason: quick reply did not attribute