---
title: "report performance tuning | Skills We Assign For | Azendo"
description: "Making reports fast — model, query and aggregation, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/report-performance-tuning/"
---

[Skills](https://azendo.co/skills/) Analytics and BI 

# report performance tuning.

Report performance tuning reduces the time a report takes to render, through model design, query optimisation, aggregation and caching. Slow reports are abandoned reports, regardless of what they contain.

## Where report performance tuning fits on a long engagement.

Report slowness is nearly always a model problem rather than a query problem. A poorly structured data model produces expensive queries no matter how they are written, and tuning individual queries over a bad model is effort spent at the wrong layer.

Pre-aggregation is the highest-return technique and is consistently underused. Most reports show aggregates over large detail tables, and computing those on a schedule rather than on every view converts a heavy repeated query into a cheap lookup.

## What an assigned team does with report performance tuning.

Users abandon slow reports silently. They do not file a ticket; they stop opening it and go back to a spreadsheet, and the investment in the report is simply lost without anyone recording why.

Measuring render times rather than waiting for complaints is what catches that, and it sits within an agreed [committed monthly capacity](https://azendo.co/pricing/) for analytics.

## What we use report performance tuning for.

* Fixing the model rather than the query Structure corrected, because tuning queries over a bad model has a low ceiling.
* Aggregates computed on a schedule Heavy repeated calculations precomputed rather than run on every view.
* Render time monitored Slowness detected before users quietly abandon the report.

## How report performance tuning capacity is assigned.

Report tuning is assigned inside analytics capacity, starting from the data model rather than from the slowest query.

## Roles we assign report performance tuning for

* [BI Developer Data science](https://azendo.co/services/data-science/bi-developer/)

## Service lines it sits in

* [Data science](https://azendo.co/services/data-science/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in analytics and bi

* [Tableau — skill we assign for](https://azendo.co/skills/tableau/)
* [semantic layers — skill we assign for](https://azendo.co/skills/semantic-layers/)
* [A/B testing — skill we assign for](https://azendo.co/skills/a-b-testing/)
* [experimentation design — skill we assign for](https://azendo.co/skills/experimentation-design/)
* [causal inference — skill we assign for](https://azendo.co/skills/causal-inference/)
* [cohort analysis — skill we assign for](https://azendo.co/skills/cohort-analysis/)
* [segmentation — skill we assign for](https://azendo.co/skills/segmentation/)
* [metric definition — skill we assign for](https://azendo.co/skills/metric-definition/)

## Tell us what your roadmap needs report performance tuning for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)