-server is the single biggest help in dealing with James and memory, it has a dramatic effect on James, maing it keep going reliably long after it would previously have fallen over.
I believe this is largely owed to more aggressive garbage collection in the server vm. From what I've seen it loooks like it's based upon the premis that the gc will have to interrupt something because load will be steady, therfore gc is carried out when it is needed not just when its convenient.
You can reduce the impact of this somewhat by also specifying -Xnoincgc (check the docs to see what to do) in suns jvm. This turns on incremental garbage collection which has an overall hit on speed types of performance but removes the embarassing pauses which Java exhibits when using the standard gc behaviour.
What you end up with is lower performance but a much more stable installation. == solve your load issue with new/more hardware.
Seems like there are a LOT of good suggestions going around. I would love it if someone would add a Wiki page to capture all these tips and tricks as the listserv archives aren't always the most accessible.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
