Performance

Find the bottleneck, pull the right lever, and make slow reports fast.

Holistics report performance is bound by the slowest of these stages:

Pre-query processing: parsing, permission checks, query plan
Job queuing: waiting for an available worker
Query execution: running on your data warehouse
Result transfer: moving the result set from your data warehouse to Holistics
Post-query processing: caching and result assembly
Browser render: drawing the visualization

For the full breakdown, see Report Running Mechanism.

Common levers

A few high-leverage ways to make things faster, before you go deep into diagnosis.

Tune the underlying datasets and models to speed up SQL execution, usually the biggest bottleneck.

Fewer rows means faster transfer and rendering. Apply filters, limits, and group small series into "Other".

Each widget spawns its own job. Aim for 10 to 15 per dashboard and use drill-through for extra detail.

Tune cache duration to the freshness and cost trade-off your dashboards need, and persist slow, stable queries.

For frequent slices over large fact tables, route queries to pre-aggregated tables transparently.

Speed up result transfer when results are large or your warehouse sits far from a Holistics region.

Queries run on your warehouse, so its processing power and configuration set the ceiling.

Symptom-based diagnosis: Performance Troubleshooting walks through what each report-loading status means and how to fix it.
Slow jobs you can't pin down: Report Slow-Running Jobs: how to file an actionable support request.

If none of this matches what you're seeing, contact [email protected] with the URL, the slow status, and a screenshot/recording.