Monday April 16, 2007
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
truefor 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
Search This Site
Recent Entries
- Raible Road Trip #13
- The good ol' Job Hunt
- How to use GWT 2.0 with Maven and Generate SOYC Reports
- JSON Parsing with JavaScript Overlay Types in GWT
- A Fun Father's Day at Great Sand Dunes
- Going to the Great Sand Dunes for Father's Day
- Implementing OAuth with GWT
- Enhancing Evite.com with GWT and Grails
- 2nd Row at Red Rocks and Elephant Rock Ride
- Creating a Facebook-style Autocomplete with GWT
Posted by anjan bacchu on April 16, 2007 at 08:45 PM MDT #