> -----Original Message----- > From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Sent: Sunday, April 14, 2013 5:52 PM > To: Tomcat Users List > Subject: Re: Re : Memory leak in Tomcat 6.0.35 ( 64 bit) > > I've had people tell me that I should run with the biggest heap I "can > afford" meaning both financially - 'cause you have to buy a bunch of > memory - and reasonably within the constraints of the OS (it's not > reasonably to run a 9.9GiB heap with 10GiB of physical RAM, for > instance). The reasoning is twofold: > > 1. If you have leaks, they will take a lot more time to blow up. > (Obviously, this is the opposite of my recommendation, but it's worth > mentioning as it's a sound argument. I just disagree with the > conclusion). If you watch the heap-usage profile over time, you can see > it going up and up and instead of getting an OOME, you can predict when > it will happen and bounce the server at your convenience. > Chris - My back-argument to this reasoning is this:
It's fine for the production side in order to maximize uptime while you investigate the cause of the leaks. Then I recommend your suggestion for the Dev/Test environment to isolate the cause(s). Once fixed, bring the production side back to something resembling normality. Jeff --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
