I'm not familiar with Derby, so I'm not going to be able to offer any advice.
The biggest killer will just be the number of db interactions. If you can create a view, or a stored procedure so that you're only doing one db interaction per page, then you'll see a huge difference. For example, if you have some complex code that queries different tables, and does a lot of processing to determine results, then a stored procedure will save a lot of time and effort. Other than that, my advice would be to benchmark the different queries ( using something like Jmeter) and fix what seems the slowest. 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 4:26 PM > To: Tomcat Users List > Subject: Re: Tuning Tomcat , i need some advice > > Thank you for reply. > > George Sexton wrote: > > 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: > > > Indeed some pages of my web application will cause more than > 4-5 select > statement over tables with more than 50,000 records. > will a dual processor server handle this loads ? I used derby > as database . > > 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. > > > How i can tune the database code ? > i just once worked with db2 , it has some facilities that bring up a > plan (execution path and detailed information about each step) of > statement and allow user to tune the database operations base on its > step and time that each step consumed , now how i can find such > facilities for derby ? > > Thank you > > 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] > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
