« JSF still sucks? | Main | Comparing Java Web... »
20070416 Monday April 16, 2007

Configuring Tomcat for Production From The Atlassian Developer Blog:

You appear to be running Tomcat in development mode. (http://tomcat.apache.org/tomcat-5.5-doc/jasper-howto.html)

This means that source of every JSP is held in memory to provide detailed messages in the event of an error. If you have large JSPs this will hurt. It looks like this accounts for 50MB+

From Tomcat's Production Configuration documentation:

The main JSP optimization which can be done is precompilation of JSPs. However, this might not be possible (for example, when using the jsp-property-group feature) or practical, in which case the configuration of the Jasper servlet becomes critical.

When using Jasper 2 in a production Tomcat server you should consider making the following changes from the default configuration.

  • development - To disable on access checks for JSP pages compilation set this to false.
  • genStringAsCharArray - To generate slightly more efficient char arrays, set this to true.
  • modificationTestInterval - If development has to be set to true for any reason (such as dynamic generation of JSPs), setting this to a high value will improve performance a lot.
  • trimSpaces - To remove useless bytes from the response, set this to true.

Seems like good information to know. Posted in Java at Apr 16 2007, 04:05:03 PM MDT 1 Comment

Comments:

hi there, thanks for the tips. I tried trimSpaces a few years ago and I had some trouble -- has the behavior changed ? Did you have any issues ? The new trick I learnt is genStringAsCharArray(in tomcat 5 it is called genStrAsCharArray) BR, ~A

Posted by anjan bacchu on April 16, 2007 at 08:45 PM MDT #

Post a Comment:
  • HTML Syntax: Allowed