Skip to main content

Performance Troubleshooting

Central Doc

Visit Performance Optimizations to see the central doc on Performance.

A. "My report takes too long to load"​

Try to narrow down to symptom B, C, E, F, or G.

B. "My report takes too long at Pending status"​

performance-perf-pending performance-perf-pending3

Causes:​

Resolution:​

  1. Validate the cause using Blocked Jobs Analysis of Job Performance Analytics
  2. Possible optimizations:

C. "My report takes too long at Running query... status"​

performance-perf-running

Causes:​

Without Holistics Canal​

With Holistics Canal​

  • The query execution is taking long on your Data Warehouse -> Go to section D

Notes:​

  • How to validate the cause?
    • Compare Holistics Job Logs against your Data Warehouse logs. (Holistics Job Logs are accessible in Job Monitoring page)
    • Compare against the execution/query plan on the Data Warehouse (e.g. using EXPLAIN ANALYZE). Learn more
    • Try downloading the data from the Data Warehouse console and time the download

D. "My query takes too long to run on the Data Warehouse"​

Causes:​

  • The query is costly/complex and hence it is slow by itself
    • -> Check the execution/query plan on the Data Warehouse (e.g. using EXPLAIN ANALYZE). Learn more
    • Possible optimizations:
      • Pre-aggregate data, either manually or by using Holistics Aggregate Awareness
      • Use Query Parameters to push down predicates and utilize database indexing more efficiently
      • Persist your query by using Model Persistence (or database materialized views, dbt persistence, etc.)
      • Add indexes/clustering/partitioning on the Data Warehouse.
  • The Data Warehouse is overloaded
    • -> Increase resources (e.g. CPU, Memory) of the Data Warehouse

Head over to Investigate and troubleshoot data warehouse issues for detailed instructions on how to deal with this issue.

E. "My report takes too long at Processing result status"​

performance-perf-process-result

Causes:​

  • The query result is too big and hence it is slow to cache or render the result in Holistics

Resolution:​

F. "My report takes too long at Loading status"​

performance-perf-loading

Possible causes:

  • Holistics is taking long to perform pre-processing on your report. Usually, this is because your Modeling code is large or complex.
  • The browser is taking long to communicate with Holistics servers, typically because:
    • Of your internet connection
    • You are physically distant from Holistics Data Center -> You can migrate to a Holistics Data Center that is physically closer to you.
    • And/or your Modeling code is large

For the cases where your Modeling code is large or complex, Holistics is continuously improving to make this "Loading" step faster.

In any case, you can reach out to us at [email protected] and share with us:

  • The URL of the page you are visiting
  • The title of the Report or Dashboard that is taking too long at Loading status
  • The duration of the Loading status

G. "My report takes too long at Fetching result... status"​

performance-perf-fetching-result3
Note

This loading status only appears when Holistics Canal is enabled.

Causes:​

  • The query result is too big and hence it is slow to fetch the result to Holistics.

Resolution:​

"My users complain about performance but I don't know where to start"​

Use Job Performance Analytics

Others​

If:

  • Your performance issue does not match any symptom above
  • Or the suggested solutions do not work for you

Please reach out to Holistics Support, and make sure to include these details, as many as possible:

  • The URL of the page where you experienced the issue.
  • The duration of the loading time that you experienced, and your expectation of the loading time.
  • Screen recordings or screenshots of the issue.
  • The steps that you took that led to the issue.
  • If a Job is involved, please also follow Support for slow Jobs.
Let us know what you think about this document :)