Howdy, >Well not really; we know that we are running Tomcat, a web container which >has its own (fixed) characteristics. It is a server side app which is >processing non state based transactions which are thus highly like to >involve a lot of objects being created and destroyed without too many >hanging around for long; the details of the webapp, unless it is highly >unusual, are likely not to matter particularly. This is a rule of thumb >not an exact science and the vast majority of people who run Tomcat would >benefit from running in such a configuration (or playing with it to see >what the effects were)
I disagree ;) Every time I've tuned a webapp for pay, both transactional and not, both full J2EE and "just" servlets/JSPs, the above has been false. The webapp's specific implementation matters far more (typically 3-4 orders of magnitude) than the container implementation, especially for a mature container which has been tuned repetitively and carefully over time. It's precisely because of this, and because as you say performance tuning is not a science, that a rule of thumb is as likely to hurt as it is to help if blindly applied. > read Sun's own tuning documentation and you will >see the default settings are not said to be suitable for the majority of >server apps. I appreciate the pointer - I used to help write them ;) Good luck, however, as it's always YMMV with these things. Yoav Shapira 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
