On Nov 24, 2012, at 5:22 AM, SMX25 <[email protected]> wrote:
> Since the other container on the production is working without any explicit > PERM GEN setting, I would not want to go with the approach of increasing the > PERM GEN size unless I know the root cause of the problem. You might simply be on the cusp of the right amount of memory. The PermGen setting that comes with containers is an approximation, there's no way to get it right for every deployment -- too large wastes memory, too small is fatal, and every deployment has a wide variety of deployed classes. The best way for you to find the answer for your environment is to use a profiler such as YourKit and look for yourself. Start by looking at your current configuration to see how much PermGen space is available, then bump it up by 50% and see if it remains within 10-20% of the original number in all cases. If so, leave it at that number and profile it in production with lots of users as well. There's no sense not knowing what's happening there. Brian
