What are paused values ​​in the GC_CONCURRENT log messages?

Question

I am trying to examine the behavior of a new matching garbage collector in GingerBread (2.3).

Can someone please explain these log lines in detail (especially the "paused" parts of GC_CONCURRENT and GC_FOR_MALLOC )?

 12-24 10:20:54.912 D/dalvikvm( 414): GC_CONCURRENT freed 510K, 57% free 2529K/5831K, external 716K/1038K, paused 8ms+5ms 12-24 10:20:54.963 D/dalvikvm( 414): GC_FOR_MALLOC freed 510K, 57% free 2529K/5831K, external 716K/1038K, paused 47ms 

Answer 1

• GC_CONCURRENT heap is (almost) full. Therefore the simultaneous gc outputs in

• freed 510K - Amount of freed memory

• 57% free - Memory after free%
• 2529K/5831K - Actual memory on the heap
• external 716K/1038K - External memory (memory that is not in dvm)
• paused 8ms+5ms - time spent on GC

especially the "suspended" parts

For parallel collections, there are two pause periods. One of them is at the beginning of the collection, and the other is closer to the end. For a non-automatic collection, there will be only one pause time.

Answer 2

If you haven’t already done so, check out this video: http://www.google.com/events/io/2011/sessions/memory-management-for-android-apps.html