MichaelEGR wrote:Perhaps profile your app first to learn where the actual problems are occurring. You can do this by using the ddms tool and hitting the 2nd button from the left to dump an hprof file or use the Debug static methods to programmaticly dump an hprof file. Then use the hprof-conv tool:
http://developer.android.com/guide/deve ... -conv.html
Load two comparison (before and after) init or major resource allocations and then perhaps a 3rd or 4th snapshot during runtime and evaluate where your problems are. Until you do this you are grasping at straws so to speak and only working with assumptions which can easily turn out to be wrong. You may be doing something inefficiently elsewhere, etc.
I use YourKit for my Java profiler. For a free one I've read that MAT is good too, but I've not used it:
So I definitely advise you get a real picture of what is going on before optimizing the wrong part of your app.
I take it hprof and logcat results are different.
I'm new to both Java and Android - so am soaking up as much good-practice as I can find!
I had come across MAT before - but it looked like it was more for non-android Java apps. I'll have another look.
Time to roll my sleeves up!
Users browsing this forum: No registered users and 5 guests