Database interaction is by far the major issue. In my application, a page with no db interaction runs in something like 80ms, while a page with DB interaction takes something like 350-400ms. There's no silver bullet to tuning tomcat applications, and most of the advice you'll get here won't make any difference (use this connector, instead of that). So, my advice is:
1) Using JDK 1.5. It can be up to 25% faster than 1.4 2) Use the server JVM 3) Allocate sufficient memory 4) Start tuning your application. Look at query execution times, and the number of DB Interactions per page. Reduce the number of interactions by using Stored procedure, or views. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 > -----Original Message----- > From: Legolas Woodland [mailto:[EMAIL PROTECTED] > Sent: Monday, January 30, 2006 1:57 PM > To: Tomcat Users List > Subject: Tuning Tomcat , i need some advice > > Hi > Thank you for reading my post. > I have an application which will handle about 30 hit per second with > Tomcat 5.5.* (* wil be one of 15 or 12) > Now i need some advice about tuning tomcat to perform the best under > this condition > I read something so far , things like : > > use Java server mode > increase the heap > > Where i can find more reference and how to(s) or step by step > manual to > tune tomcat. > in condition that we have 30 hit/sec ,how much large connection pool > should be ? > is there some refrences about tuning connection pool? > > Thank you > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
