[Shib-Users] IDP 2.3.0 memory hungry? Or something else in our setup?

[Chad La Joie]

On Thu, Aug 4, 2011 at 19:16, Russell Beall <beall at usc.edu> wrote:
> I'm not sure what the default PermGen size is, but Chad probably suggested removing it because the default is workable now.  I saw 128M mentioned somewhere as the latest recommendation (when I looked a few months ago), so that is what I am planning to change it to.  In production, mine is still set to 1G on the 2.1.5 release where the metadata loading hadn't yet been streamlined.

Default perm gen is 64M on most JVMs on most systems.  This is enough
in most cases today.  The tuning guide for the IdP recommends 128M
just to catch the people with very large deployments.

Note, 2.1.3 was the last time the especially high PermGen was really
necessary.  Prior to that there was a bug in Xerces that prevented
loaded XML documents from going away if you pooled parsers and then a
bug in the IdP that resulted in the same thing.

> The histogram numbers you reported indicated that the actual Tomcat JVM had not filled up even remotely, so even though the system reported missing memory, it wasn't actually a problem.  It is likely you do not have a problem with the actual JVMs.

Yeah, I keep saying this over and over again.  You *can not* use tools
like top in order to gauge the amount of memory the JVM is actually
using.

-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered