This article addresses a possible issue where reports are running slow. This is primarily a legacy issue, as the reporting engine was greatly improved in Chronicall version 3.6.56. It can still be good to reference, as it covers general report optimization.
- As of Chronicall version 3.10, 64-bit Java is built in and by default increases the memory allocation even more.
An outdated report that has not been upgraded to our new reporting engine or not enough memory has been dedicated to the Data Grid. It is always recommended that you update to the most recent version of Chronicall available on the download page linked below.
As of Chronicall version 3.6.56 a new reporting engine was released that will speed up report time greatly by utilizing the Chronicall server's RAM. This reporting engine is included in Chronicall versions 3.6.50 and above.
- If you have not updated Chronicall to the 3.8 or 3.10 branches, please do so now. Linked here is our download page and update instructions.
- Once updated, some reports that were previously built may still be using the old reporting engine. To upgrade your reports to use the new, faster reporting engine, please refer to our Upgrade Reports article.
Increase Datagrid Memory
- Lastly, the new reporting engine uses what we call a Data Grid. The default values are valid for the majority of our users. If you find that you need to change these values, such as increasing or decreasing memory usage at the bottom of this article, the definitions can be found in our Data Grid article.