tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark H. Wood" <mw...@IUPUI.Edu>
Subject Re: RE : Tomcat 6.0.35 Crashed again
Date Thu, 11 Apr 2013 14:41:22 GMT
Really, no one else can tell you what settings to use.  The best we
can hope for is some accepted rules of thumb *as starting points* for
further tuning.

I'd suggest choosing a tool that lets you easily monitor the memory
pools, and checking it frequently as you adjust the pool sizes.  If
your applications are not leaking memory, the pools should each expand
to a certain size and then tend to stay there.  I would set each
pool's initial size slightly larger than its steady-state size, and
set some additional headroom on its maximum size to cope with
unpredictable demand bursts.  (Actually I would leave most of them
alone and just tune the ones that seem significantly out-of-tune.)

I suggest continuing to monitor memory behavior on a regular basis.
Your load probably varies over time, and different versions of code
behave somewhat differently.  I have a repeating reminder on my
calendar to check my Tomcat instances weekly.

I use PsiProbe for peeking inside Tomcat, but there are a number of
other good tools.

As your Tomcat tuning progresses, you'll find what its overall size
"ought to be", and can then consider tuning and perhaps resizing the
surrounding system.  A well-tuned servlet container running in a
poorly-tuned OS or undersized hardware will still underperform.  The
general plan here is the same:  start with an educated guess, observe,
adjust, monitor....

-- 
Mark H. Wood, Lead System Programmer   mwood@IUPUI.Edu
There's an app for that:  your browser

Mime
View raw message