On Jul 24, 3:40 am, "brian.schimmel" <[email protected]> wrote: > Interestingly, while doing some benchmarking it turned out that the > real heap size and heap usage is not increased by this. I called > setMinimumHeapSize jsut before the caching/prebuffering starts. I've > compiled my app with different values and used the eclipse DDMS view > to query the heap usage at three important times in my application > life cycle:
I would expect it to modify the "soft" limit, i.e. the point you're allowed to grow to before a GC happens. The full size of the heap is determined by the -Xmx "command line" argument, passed in during VM creation by the app framework. One thing that may be useful in your experiments: the system event log receives a lot of detail about the state of the heap after a GC. You can view it with the dalvik/tools/gclog.py script. A copy is available from http://bigflake.com/gclog.py.txt . (Set debug = True in handleGcInfo() to get the full dump.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
