How to Disable automatic deployment on production servers using Tomcat

Tomcat can be configured to check on a regular basis if the files of your application have changed on disk, and redeploy the application if they did. As checking if files have changed is incredibly cpu and memory intensive it is recommend to disable the automatic web application redeployment feature, on production servers which is enabled by default. Modify it so that it resembles the snippet below:

<host appbase="webapps" autodeploy="false" name="localhost" unpackwars="true" xmlnamespaceaware="false" xmlvalidation="false" />

• For more information on autodeploy, see http://tomcat.apache.org/tomcat-7.0-doc/config/host.html#Common_Attributes

Other Performance Tips:

• Measure and Test
  • Test DB Queries with DBTester
  • Do Performance Testing with JMeter
  • Measure Ad Hoc Performance
• Ad Hoc
  • Set query limits on the "Ad Hoc Options" page
  • Modify the Ad Hoc caching values if your data does not update constantly
• Tomcat
  • Compress HTTP responses at the Tomcat level
  • Increase the maximum thread count at the Tomcat level
  • Set up a cache filter for Tomcat or JBoss
• Database
  • Index columns in the database to speed up domain-based reports
  • Set the fetch size in the jasperreports.properties file to modify the number of rows to fetch
• JasperReports Configuration Items
  • Modify Virtualizer Settings for Very Large Reports
  • Modify the jasperreports.properties file to disable multi-line data processing

• Back to JasperReports Server Performance Tips and Tricks