Two things to think about in addition to the recommendation Chuck mentioned.
1. For small requests having a large new generation in the heap helps. This helps with the short term objects in the heap to get collected. 2. Lots of small disk IO may slow you down also. Remember http is synchronous and has to wait for disk IO unless it is spawned off to an independent thread. Hope this helps. -Tony --- On Thu, 9/1/11, Caldarale, Charles R <chuck.caldar...@unisys.com> wrote: > From: Caldarale, Charles R <chuck.caldar...@unisys.com> > Subject: RE: Performance for many small requests > To: "Tomcat Users List" <users@tomcat.apache.org> > Date: Thursday, September 1, 2011, 9:58 AM > > From: David kerber [mailto:dcker...@verizon.net] > > > Subject: Re: Performance for many small requests > > > Is there any indication from what I've said that > > I need a larger heap? > > Don't think so, but GC logging will tell you for > sure. The compressed OOPs capability with a small heap > should not incur any encode/decode overhead and should > improve cache hit rates. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR > OTHERWISE PROPRIETARY MATERIAL and is thus for use only by > the intended recipient. If you received this in error, > please contact the sender and delete the e-mail and its > attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
