You are really just starting document the issues necessary for running a high volume site.
The URL http://www.mhsoftware.com/resources/top10asp.html Has some things that are IIS specific, but also apply to Tomcat applications: Specifically: Store as little as possible on the session. I'm working on an app right now, where the author decided storing the db connection on the session was the way to go. Watch contention. Use an automated code analysis tool like PMD or Findbugs to eliminate bad and redundant code. PMD will detect things like string concatenation in loops, using string concatenation in StringBuffer.append() methods, and other non-optimal techniques. Stress test using a tool like Jmeter. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 > -----Original Message----- > On Wed, 09 Feb 2005 00:18:52 +0100, Wojciech Sobczuk > <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I have collected my experiences with running a heavily > loaded (and soon > > to be high availability) tomcat setup in a paper available here: > > http://brandlay.com/wojtek/publ/tomcat.jsp > > Have a look if you're interested and please email any > comments directly > > to my email. > > > > Thanks! > > > > -- > > Wojciech Sobczuk > > [EMAIL PROTECTED] > > +48 605 607 170 > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
