I'd ditto George's advice.
Unless your page generation code is really trivial, it will be the major
determining factor of your performance -- not Tomcat.
Thus the first steps are general JVM tuning and application code
profiling and tuning. Only after you've selected the right JVM, the
right basic options, fed it enough memory, and tuned your code is it
generally time to turn to further Tomcat tuning.
--
Jess Holle
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:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
