Databases
StackOverflow2013
Postsdbo
POJava Garbage Collection Log messages
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJava Garbage Collection Log messages
    text
    copied!<p>I have configured java to dump garbage collection information into the logs (<a href="http://wiki.zimbra.com/index.php?title=When_to_Turn_On_Verbose_GC" rel="noreferrer">verbose GC</a>). I am unsure of what the garbage collection entries in the logs mean. A sample of these entries are posted below. I've searched around on <a href="http://www.google.com/search?q=PSYoungGen" rel="noreferrer">Google</a> and have not found solid explanations. </p> <p>I have some reasonable guesses, but I'm looking for answers which provide strict definitions of what the numbers in the entries mean, backed up by credible sources. An automatic +1 to all answers which cite sun documentation. My questions are:</p> <ol> <li>What does PSYoungGen refer to? I assume it has something to do with the previous (younger?) generation, but what exactly? </li> <li>What is the difference between the second triplet of numbers and the first?</li> <li>Why is a name(PSYoungGen) specified for the first triplet of numbers but not the second? </li> <li>What does each number (memory size) in the triplet mean. For example in 109884K->14201K(139904K), is the memory before GC 109884k and then it is reduced to 14201K. How is the third number relevant? Why would we require a second set of numbers?</li> </ol> <blockquote> <p>8109.128: [GC [PSYoungGen: 109884K->14201K(139904K)] 691015K->595332K(1119040K), 0.0454530 secs]</p> <p>8112.111: [GC [PSYoungGen: 126649K->15528K(142336K)] 707780K->605892K(1121472K), 0.0934560 secs]</p> <p>8112.802: [GC [PSYoungGen: 130344K->3732K(118592K)] 720708K->607895K(1097728K), 0.0682690 secs]</p> </blockquote>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload