Note that there are some explanatory texts on larger screens.

plurals
  1. POJava HotSpot 1.6 VM, Garbage Collection - Scary PermGen
    primarykey
    data
    text
    <p>My app shows rising 'Old Generation'/'Tenured Generation' size, and when this reaches the max limit for 'Old Gen', then suddenly PermGen size increases. Here are my generation sizings:</p> <pre><code>-Xmx1200m -Xms1200m -Xmn450m -XX:MaxPermSize=600m -XX:+UseParallelGC </code></pre> <p>This is on 32 bit Fedora so can't have a bigger heap than this.</p> <p>The app is not doing any fancy classloading, though it is using Spring IOC and Hibernate, the Spring App-context.xml defines some 1000 Beans.</p> <p>This app starts with 175MB PermGen, which steadily increases to ~250MB in few hrs, stays that way till Tenured Generation reached ~780 MB, then permgen jumps to ~500MB while Old Gen drops to ~500MB.</p> <p>This forces me to restart the App on daily basis, and gives me real scare of looming OutOfMemory Error.. Any insights would be very helpful.</p> <p>Thanks Gala101</p> <p>13/May: Could someone please throw light on what happens when 'Old Gen' is garbage collected? <br /> Does the jvm put collections from 'Old Gen' into PermGen? <br /> My PermGen spike comes only when collection happens from 'Old Gen', also decrease in OldGen size closely matches increase in PermGen size.<br /> PS: I don't do any live deploy/undeploy as that's sure to eat up PermGen.<br /> Below is a current spanshot from my monitoring page: (the committed part had just jumped from ~250 MB to 500 MB)</p> <pre><code> PS Perm Gen Type Non-heap memory Usage init = 16777216(16384K) used = 254453736(248489K) committed = 504954880(493120K) max = 629145600(614400K) Peak Usage init = 16777216(16384K) used = 254453736(248489K) committed = 504954880(493120K) max = 629145600(614400K) Collection Usage init = 16777216(16384K) used = 252421536(246505K) committed = 504954880(493120K) max = 629145600(614400K) </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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