Ways to optimize Android App code based on function call stack?
Posted
by K-RAN
on Stack Overflow
See other posts from Stack Overflow
or by K-RAN
Published on 2010-05-28T18:47:13Z
Indexed on
2010/05/28
18:52 UTC
Read the original article
Hit count: 213
I've been told that Android OS stores all function calls in a stack. This can lead to many problems and cause the 'hiccups' during runtime, even if a program is functionalized properly, correct?
So the question is, how can we prevent this from happening? The obvious solution is to functionalize less, along with other sensible acts such as refraining from excessively/needlessly creating objects, performing static calls to functions that don't access fields, etc...
Is there another way though? Or can this only be done through careful code writing on the programmers' part? Does the JVM/JIT automatically optimize the bytecode during compile time to account for this??
Thanks a lot for your responses!!
© Stack Overflow or respective owner