performance-observabilityAnswer last reviewed July 2026

You'll notice experienced engineers basically refuse to look at average latency. Why is that, and what do they look at instead?

A strong answer thinks in percentiles and histograms instead of averages, and can explain why the tail is what users actually feel

What an AI-prepared candidate might say

Averages hide the tail, basically. If most requests are fast but some small fraction are really slow, the average still looks fine while those users are having a terrible time. p99 is the value that 99% of requests come in under, so it captures that slow tail, the worst case real users actually hit. That's why people watch percentiles like p95, p99, p99.9 instead of the mean. And to compute percentiles correctly you need the distribution of latencies, which is what histograms give you. They bucket the response times so you can calculate percentiles and aggregate across servers. A single average per server can't really be combined in any meaningful way. The tail matters too because in systems making lots of calls, the slow ones end up dominating the overall response time. So you track latency as a histogram and watch the high percentiles, and those tell you what your slowest users are experiencing.

Senior
Locked

What an average quietly erases, why a high-fan-out request lives in the tail, and why you can't just average percentiles across your hosts.

Unlock the depth
Staff
Locked

How histograms let you aggregate latency correctly, why one slow dependency ends up dominating a fanned-out request, and which percentile you actually hold yourself to.

Unlock the depth
Follow-up chain
You'll notice experienced engineers basically refuse to look at average latency. Why is that, and what do they look at instead? | NodeBook