5 ms·

In some environments beware of creating new types and objects: http://developer.android.com/training/articles/perf-tips.html#ObjectCreation http://developer.and

• ygra 13y ago
  Yes, I noticed that some time ago and ended up rewriting parts of the application (and also avoiding generics, instead opting for HPPC). What annoys me a bit is that Dalvik has dramatically different performance characteristics from normal Java which necessitates relearning all this stuff. Nice article though and I wish I had found it sooner.
• jimmaswell 13y ago
  This seems to paint the JIT as something that hurts performance instead of helps it, is that true on Android?
  • edderly 13y ago
    It relates to the behavior of the garbage collection scheme used by dalvik which is a mark and sweep approach. When the GC runs, that’s all the VM is doing. It’s pointed out that a generational garbage collector would be more efficient allocating memory presumably there is a trade off in terms of the overall memory footprint.