Where the nanoseconds go.
I once spent two weeks shaving microseconds off a hot path. A competitor beat us anyway, with a shorter cable and a better switch. This scale is why: eight orders of magnitude, from a cache hit to the microwave link between Chicago and New Jersey, and every value links to its source.
Drag the cursor or use the arrow keys
- Main memory reference ~100 ns Big-O Was Never the Bottleneck. The Cache Line Was. (opens in a new tab)
- Kernel bypass (Onload), TCP half round trip 3.1 µs Arista and Solarflare low-latency white paper (2011) (opens in a new tab)
- Next-generation firewalls, UDP at 90% load 7–177 µs NSS Labs, NGFW performance report (2018) (opens in a new tab)
- Linux kernel TCP stack, half round trip 8.1 µs Arista and Solarflare low-latency white paper (2011) (opens in a new tab)
- Microwave, Chicago to New Jersey 3.982 ms Quincy Data and McKay Brothers (2016) (opens in a new tab)
- Treasury futures and cash, lead–lag offset ±5 ms Dobrev and Schaumburg, Liberty Street Economics (2015) (opens in a new tab)
Every category is switched off.
A dot is a single value, a bar a range. Each figure is as its source states it: datasheets, benchmark reports, papers. The argument around them is in two pieces of The Converging Line: the cache line (opens in a new tab) and the cable (opens in a new tab).