Linked by chandler on Sun 16th May 2010 19:28 UTC
Permalink for comment 425051
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2009-06-30
It is true that JIT may slow down a branchy code, but that's not where the performance bottleneck usually lays in. Whenever the application runs slowly it is almost always due to some heavy data shifting going on. In other words, applications that currently consume 5% of CPU time will perhaps start consuming 10%, and these wanting 500% may find 100% enough.
Another thing to look at is the garbage collector - I'm not sure how Dalvik's one performs here but allocation tends to be a major factor in OO languages execution speed.