Good videos, with context.
"How NOT to Measure Latency" by Gil Tene

"How NOT to Measure Latency" by Gil Tene

Strange Loop Conference
9 HN recommenders · discussed 2015–2026
Open YouTube ↗

About this video

Gil Tene of Azul Systems explains common pitfalls in measuring latency and response time, including why averages mislead and the problem of coordinated omission. He introduces open source tools like HdrHistogram for better measurement and reporting.

Why it appears in the archive

The canonical recommendation whenever percentiles, tail latency, load testing or averages come up, described by some as life changing.

AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.

From the Hacker News discussion

vikiomega9 · 2016-08 · strong rec

Doesn't this depend on how "tuned" your subcomponents are? If I had a system that's supposedly heavily optimized, I would simply start seeing the worst-case latency on a higher percentile, 99.9th and so forth. Gil Tene has an excellent talk[1] on this. [1] [VIDEO]

Read original comment ↗
Rafuino · 2019-04 · strong rec

This topic always leads me to think about this great talk from Gil Tene on how NOT to measure latencies (basically, don't use averages!). [VIDEO] I'm also a huge fan of how Dormando showed latency distributions in one of his recent Memcached Extstore posts. The default is 95th percentile but you can change the percentile to what matters to you (i.e. 99th percentile if you ask me!). Scroll down to see what he did and play with it. [LINK]

Read original comment ↗
wmfiv · 2020-04 · strong rec

This a life changing video by Gil Tene on this topic. Bottom line is because of the number requests to support a single customer "request", the high percentiles are the ones that actually matter. [VIDEO]

Read original comment ↗
leetrout · 2023-05 · strong rec

We use locust at work but I HIGHLY recommend wrk for a very robust yet simple load testing tool. [LINK] And of course, this talk by Gil Tene is fantastic if you're interested in load testing stats [VIDEO]

Read original comment ↗
telotortium · 2017-02 · rec

Gil Tene has an entire talk about this point called "How NOT to measure latency" ( [VIDEO] ). In many circumstances, a web service (either server or client) has large numbers of dependencies, so a user only has to hit 95th-percentile latency for one dependency to have their overall latency significantly hurt. In other words, users may encounter the "rare" bad case on a majority of requests. Thus, even higher percentiles should be tightly controlled in order to truly keep a web service's overall latency under control.

Read original comment ↗
latch · 2018-10 · rec

Worth watching is How NOT to Measure Latency: [VIDEO] The speaker Gil Tene is also the author of the HdrHistogram which addresses this articles point: [LINK]

Read original comment ↗
allanrbo · 2020-03 · rec

The "how not to measure latency" talk by Gil Tene is another really good explanation of this topic: [VIDEO]

Read original comment ↗
agallego · 2020-05 · rec

who cares about lower percentage tiers in the world of big data? what does the p30 or 50 even matter at large scale? See Gil Tene's talk on how not to measure latency. [VIDEO] What matters is what most of your customers will get - p99, p999, p9999, p100.

Read original comment ↗