Guides
How to track build duration percentiles
Average build time looks fine but developers still complain.
4 min read
Average build time looks fine but developers still complain.
Why it happens
The mean hides the slow tail. Developers remember the p95 run, not the median one.
How to fix it
- Track p50 and p95 per workflow, not just the mean
- Alert on p95 regression rather than on absolute duration
- Segment by cache hit and miss — they are effectively two different distributions
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to collect runner metricsYou cannot tell whether a job is CPU-bound, memory-bound or disk-bound.How to export CI traces with OpenTelemetryCI timing data lives in a separate tool from the rest of your observability.How to query CI data programmaticallyYou need CI data in a dashboard or a weekly report.How to run a weekly CI health reportCI degrades gradually and nobody notices until it is bad.