Hi,
I think the first tip of advice should always be: tune your app first.  Profile it, 
design for performance from the ground up, make it scream.  This will take most of 
your performance tuning time and will net you most of the wins.

Then you get around to tuning the server.   Ideally, you should have a concept of what 
sort of traffic you expect.  Users per day, peak users per minute, that sort of 
information.  Configure the number of processing threads accordingly (minProcessors, 
maxProcessors, acceptCount parameters in server.xml).  Stress-test these modifications 
using a tool like wget, JMeter, LoadRunner, whatever you like.  But do test, document 
your results between runs so that you can compare them in a statistically significant 
way.

Don't forget to tune the JVM runtime parameters, especially if you have a 
memory-intensive application.  The various heap size parameters, garbage collection 
parameters can make a dramatic difference in performance.  Go to the Sun site and look 
at the JVM runtime options page.

Obviously, all the above is very general.  What it comes down to is that tuning is 
very specific to your app, and apps have very different performance characteristics.  
Good luck ;)

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: David LAGARDERE [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, September 10, 2002 6:01 AM
>To: [EMAIL PROTECTED]
>Subject: Performance Tuning
>
>Hi.
>
>I would like to know if there are some
>known tips to tune Tomcat 4.0 performances over
>IIS 5.0. Does isolation degree of Jakarta application
>import (appart from security considerations) ? Should
>workers be added and load balanced ?
>Don't hesitate to give me some advices.
>
>Thanks in advance.
>
>___________________________________________________________
>Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
>Yahoo! Mail : http://fr.mail.yahoo.com
>
>--
>To unsubscribe, e-mail:   <mailto:tomcat-user-
>[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:tomcat-user-
>[EMAIL PROTECTED]>

This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to