Our magnolia application (just public) uses about 50m Perm Gen with about 9k classes loaded. You double that and it still fits into 128m [*]. If you want ironclad cover go for 256m. But I see no point in going to 512m.
[*] author and public in the same tc are unlikely to use double the Perm Gen since the string intern pool is shared Cheers Philippe Will Scheidegger wrote: > > So what would you consider "reasonable" for a Tomcat running an author > and public instance of Magnolia 3.6.5 and nothing else? > > -will > > On 03.04.2009, at 18:17, Philippe Marschall wrote: > >> >> Ruben Reusser wrote: >>> >>> I would suggest increasing the perm size -XX:MaxPermSize=256m or to >>> -XX:MaxPermSize=512m - Perm Size is not heap, -Xmx will not help there. >> >> 256m is huge, 512m is humongous. Eclipse with 20k+ classes easily fits >> twice into a 256m Perm Gen. >> >> Cheers >> Philippe >> >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: >> <[email protected]> >> ---------------------------------------------------------------- >> > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: > <[email protected]> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
