Quick Way to Measure Ad Hoc Performance
To get a quick idea of where the bottle neck might be, take a look at Manage => Ad Hoc Cache (logged in as superuser). There are two columns, Query and Fetch:
Value | Description |
Query (msec) |
time from when query was sent to the db until the first row was received. If this is slow then you should index better (see Index columns in the database to speed up domain-based reports below) |
Fetch (msec) |
Time from when first row was received until the last row was received. If this is slow there might be a network bottleneck. (see Set the fetch size in the jasperreports.properties file to modify the number of rows to fetch below) |
Other Performance Tips:
Measure and Test
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
- Disable automatic deployment on production servers using Tomcat
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
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now