HPjmeter 4.2 User's Guide

Table 6-2 Fields Captured in GC Log Data When Using -Xverbosegc print options (continued)
— 3: Incremental collection will fail
— 4: Linear allocation will fail
— 5: Anticipated promotion
— 6: Incremental CMS garbage collection
and m indicates the background CMS state when yielding, as follows:
— 0: Resetting
— 1: Idling
— 2: Initial marking
— 3: Marking
— 4: Final marking
— 5: Pre-cleaning
— 6: Sweeping
— 7. Abortable pre-cleaning
• When %1 is equal to 11, %2 indicates the stop-the-world phase of CMS GC, as follows:
— 2: Initial marking (first stop-the-world phase)
— 4: Final marking (second stop–the-world phase)
Program time at the beginning of the collection, in seconds
%3
Garbage collection invocation. Counts of background CMS garbage collections and other garbage collections
are maintained separately
%4
Size of the object allocation request that forced the GC, in bytes
%5
Tenuring threshold - memory allocation that determines how long newborn objects remain in the new
generation, in bytes. These spaces are reported:
%6
• Occupied before garbage collection (Before)
• Occupied after garbage collection (After)
• Current capacity (Capacity)
Eden sub-space within the new generation, in bytes. These spaces are reported:
%7,
%8,
%9
• Before
• After
• Capacity
Survivor sub-space within the new generation, in bytes. These spaces are reported:
%10,
%11,%12
• Before
• After
• Capacity
Old generation, in bytes. These spaces are reported:
%13,
%14,
%15
• Before
• After
• Capacity
Permanent generation, in bytes. These spaces are reported for storage of reflective objects:
%16,
%17,
%18
• Before
• After
• Capacity
Total stop-the-world duration, in seconds.
%19
Total time used in collection, in seconds.
%20
82 Analyzing Garbage Collection Data