Skip to main content

Tips to improve reporting performance

Since Holistics runs all of the calculations against your database, your reports' performance largely depends on the processing power of your database and data warehouse.

While we are continuously working on improving Holistics's performance, you can also use the following tips to optimize your datasets, reports and dashboards.

Related resources

Click here to see the central page of Performance Guides.

Optimize the underlying datasets and models

Optimizing datasets and models will help optimize the report's SQL execution.
And SQL execution is often the biggest bottleneck of a report's performance.

Please refer to Dataset Performance Tips.

Reduce the number of data points on a report

In general, fewer data points will lead to

  • Faster transmission of data from your Data Warehouse to Holistics
  • Faster transmission of data from Holistics server to the end-user's browser
  • Faster visualization rendering on the end-user's browser

Here are some ways you can reduce the number of data points on a report:

  • Apply Filtering
  • Apply Limit
    • To control the default Limit, go to Admin Settings -> Visualization -> Default Records Limit
  • Limit the number of series on a chart: in Visualization Settings, go to Styles -> Group small values into "Other"

Reduce the number of widgets in a dashboard

When you open a dashboard without cache or refresh a dashboard, each widget will spawn a report query job that takes up a slot in your tenant's job queue. If the number of widgets triggered is greater than the job queue limit, some widgets will be blocked until other widgets are loaded, and free slots become available.

Besides, Drill-Through is a great way to provide additional details without jamming more visuals onto the current dashboard.

Therefore, it is advisable to have maximum 10 - 15 widgets per dashboard for better report performance. This will also make your dashboards easier to navigate.

Report poor performance incidents with Holistics

If you believe the above steps are not the underlying causes of your performance issues, feel free to reach out to our support team. It is helpful to refer to this document on Best practices when reporting slow-running queries when creating a support ticket.

Let us know what you think about this document :)