Performance is a significant part for adaption of a dashboard. There can be various reasons for performance issues or slowness in the dashboard. Below are few suggestions which could be implemented to improve dashboard performance.
Issue/Introduction
Tips to improve Dashboard performance
Environment
All Supported Operating Systems
Resolution
- In most of the production databases, the tables are likely to be normalized. When such databases are used for reporting, the dashboard has to traverse across multiple tables to render the visualization, slowing down the time to render. In such cases, verify whether de-normalization of data tables is a possibility. De-normalization ensures that the query fired by the dashboard goes against one table, fetching all the required elements in one go.
- Check if any database optimization (Partitioning, Indexing etc.) could help improve the query execution time.
- Try to remove the unwanted data and columns, calculated columns, use aggregated calculations at the back end if possible and check the joins in the tables.
- Try to minimize the number of records fetched. Use exact filters to keep only the required data.
- If the dashboard is mostly displayed on the web, scheduled updates can be used to cache the data on the server. It will then be available in the web player memory and will load (almost) instantaneously.
- Consider using In-DB data. This way the data will be kept in the database, instead of fetching in the memory and the aggregations will be passed to the database, which means fewer data to be transferred to Spotfire.
Keeping in mind these suggestions while creating a dashboard will aid in improving final dashboard performance. Also, improvements in the end to end reporting landscape workflow and underlying data model should be considered for fully optimized performance.