On Apr 29, 9:41 am, Ward Willats <[email protected]> wrote:
> Oh well, I switched to gawk and did this "aeheap.awk" (android external heap):
I got a Python script working. I believe this is the second python
script I've ever written, so it's probably not going to win any style
awards.
When a GC happens you see this in the debug log (e.g. "adb logcat -v
time"):
04-29 22:18:00.224 D/dalvikvm( 195): GC freed 64 objects / 3232 bytes
in 252ms
and this in the event log ("adb logcat -v time -b events"):
04-29 22:18:00.224 I/dvm_gc_info( 195):
[7017575181485851338,-9205213429612410843,-4017630296264763397,7370389]
The monstrosity decomposes to:
> id="acore" time=252 freed=3232
> freed=64 foot=3276800 allow=3538944 objs=49152 bytes=2424832
> soft=4063232 act=2621440 allow=2621440 objs=43264 bytes=2076672
> foot=0 total=0 limit=1077248 alloc=610304
I pulled out the fields that seemed useful, yielding:
04-29 22:18:00 acore(195) softlim=3968KB, extlim=1052KB,
extalloc=596KB
freed 64 objects / 3232 bytes in 252ms
This duplicates the debug log entry from the original (mostly as a
sanity check), and shows the heap soft limit, the external allocation
limit, and the external bytes allocated.
Note that the numbers don't quite match up. This is because the event
log encodes values in a 12-bit floating point format, so you don't get
a lot of resolution, and large numbers tend to get rounded.
I put an "early release" copy here if you want to play with it:
http://bigflake.com/gclog.py.txt
It'll show up in dalvik/tools eventually.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
