Thanks Lance. I am still not clear when the classes get undeployed with 1.6 JVM and using the above start up options
Does this get undeployed on JVM restart ? OR Do the classes get undeployed by Pemgen Gc? Does Pemgen Gc work for 1.6 Version? Regards Sujatha On Sun, Jan 29, 2012 at 6:08 AM, Lance Norskog <goks...@gmail.com> wrote: > Correct. Each war file instance uses its own classloader, and in this > case pulling in Solr and all of the dependent jars uses that much > memory. This also occurs when you deploy/undeploy/redeploy the same > war file. Doing that over and over fills up PermGen. Accd. to this, > you should use both this and ClassUnload: > > > http://stackoverflow.com/questions/3717937/cmspermgensweepingenabled-vs-cmsclassunloadingenabled > > On Fri, Jan 27, 2012 at 10:59 PM, Sujatha Arun <suja.a...@gmail.com> > wrote: > > When Loading multiple solr instances in JVM ,we see the pergmen space > going > > up by about 13mb per Instance ,but when we remove the instances ,that are > > no longer needed,we do not see the memory being released .This is our > > currnt JVM startup options . > > > > -Xms20g > > -Xmx20g > > -XX:NewSize=128m > > -XX:MaxNewSize=128m > > -XX:MaxPermSize=1024m > > -XX:+UseConcMarkSweepGC > > -XX:+CMSClassUnloadingEnabled > > -XX:+UseTLAB > > -XX:+UseParNewGC > > -XX:MaxTenuringThreshold=0 > > -XX:SurvivorRatio=128 > > > > Will enabling permgen GC help here XX:+CMSPermGenSweepingEnabled? Will > the > > classes not be unloaded unless we do a server restart? > > > > Regards > > Sujatha > > > > -- > Lance Norskog > goks...@gmail.com >
