On Wed, Dec 10, 2008 at 08:52:54PM -0500, George Kozak wrote: > Here is my Tomcat configuration: > JAVA_OPTS="-server -Xms1024m -Xmx2048m -Xmn64m -Dfile.encoding=UTF-8 > -XX:+UseParallelGC -verbose:gc > -Xloggc:/dspace/dspace/log/gc.log -XX:+HeapDumpOnOutOfMemoryError > -XX:PermSize=1024m -XX:MaxPermSize=1024m -XX:-UseGCOverheadLimit"
It looks like your PermGen starts out the same size as your entire memory starting size. So, just about the first thing the JRE has to do is expand, and the amount of non-PermGen memory you have will never be more than 1G with these settings. I know Tomcat often wants more PermGen than it gets with default settings, but do you really need 1G PermGen or are you perhaps unnecessarily starving other memory pools? I'm certainly *not* a Java memory wizard, but that's what pops out at me. Have you tried e.g. LambdaProbe on the running Tomcat to see how the various pools are being used? -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Friends don't let friends publish revisable-form documents.
pgpg6G8s57Y0H.pgp
Description: PGP signature
------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
