Common performance issues on Android?

Question

What are the easiest bugs that can cause performance loss on Android?

The documentation mentions that “some floating point operations” may be “on the order of milliseconds” - did someone check this?

For discussion, suppose it runs on a G1 / similar device.

Answer 1

Performance recommendations related to rendering, see these Google I / O 2009 posts:

• Make your Android UI fast and efficient
• Writing Real-Time Games for Android

Answer 2

floating point:

G1, 400 . ints 250 .

, eclair (pre-JIT), 120 . (ints , , .) int long, float double, , , , , .

- . ( , , /, , .)

, . , , .

(eclair) . , .

---

" / Java ?", : . GC, /, , /. GC, , 24MiB . .

Answer 3

, , float, , cpu ( ) . .

, , , .

, java, java . .

Answer 4

, , . (ints float, ), , , , . 5% , , .

Answer 5

Android, . , Java -

List<String> strings = new ArrayList<String>();

Android ,

ArrayList<String> strings = new ArrayList<String>();

Answer 6

, AppInventor 2014 i3/4Gb. , , 10 - , 2000 . , , , .

, , . , - 30 . , .

It is clear that if there is a way to force a fixed point or use integers that would only help, but the scale of the problem that I came across with this tiny project is not a good omen.