Hi, We actually have several webapps (on separate tomcat instances) with very different data models and corresponding GC behaviors.
For example, we have one webapp which actually doesn't get that much user traffic, but needs to have a lot of information cached in memory for very quick retrieval once those few users ask for it. So its old generation is about 80% of the heap. We found ConcMarkSweepGC on the old generation and parallel GC on the new generation to be very good here: JAVA_OPTS='-server -Xmx1024m -Xms768m -XX:NewSize=100m -XX:MaxNewSize=200m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseParNewGC' But as I've mentioned many times before: these settings are very application-specific. I don't know of any way, other than experimentation and tuning with your own app, of finding the right settings for you ;) Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Nick Wesselman [mailto:[EMAIL PROTECTED]] >Sent: Friday, November 22, 2002 4:28 PM >To: Tomcat Users List >Subject: Re: Sun JDK 1.4 production quality? > >On Friday, November 22, 2002, at 11:33 AM, Shapira, Yoav wrote: > >> GC has markedly improved, although we did have to experiment >> a bit with the new GC options. > >What conclusions did you come to? My understanding is that >ConcMarkSweepGC might be helpful for Tomcat, since you could avoid the >problem of the OS gathering too many network connections for Tomcat >while it's garbage collecting. > >Nick > > >-- >To unsubscribe, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
