colin-scott/interactive_latencies
View on GitHub ↗ ★ 2,175 JavaScript
Jeff Dean's latency numbers plotted over time
13 mentions on Hacker News by 9 people: 0 stories, 13 comments · first 2012-12-25 · latest 2026-02-28
20082026
-
…indicates the original set of numbers were more like 10us, 250us, and 30ms. And it links to https://github.com/colin-scott/interactive_latencies which seems like it extrapolates progress from 14 years ago: // NIC bandwidth doubles every 2…
comment by vitus · 2026-02-28 · in Latency numbers every programmer should know -
…Dean (slides) - https://www.cs.cornell.edu/projects/ladis2009/talks/dean-key... - Colin Scott - https://github.com/colin-scott/interactive_latencies?tab=rea... - this post
comment by montebicyclelo · 2024-03-10 · in Latency numbers every programmer should know -
It is indeed a year. The latencies are based on the calculations done by Colin Scott in https://github.com/colin-scott/interactive_latencies and support projecting out into the future. Sorry it's not as obvious as it could be.
comment by samwho · 2024-03-10 · in Latency numbers every programmer should know -
…numbers from back then to _guess_ what future numbers would look like! (I was fooled by it too) See https://github.com/colin-scott/interactive_latencies/issues/...
comment by ZainRiz · 2022-03-04 · in How “latency numbers everybody should know” decreased from 1990–2020 -
…this tool makes inaccurate projections from 2012 data. It is not at all accurate for 2020. See: https://github.com/colin-scott/interactive_latencies/issues/...
comment by thundergolfer · 2022-03-04 · in How “latency numbers everybody should know” decreased from 1990–2020 -
It looks like that because an inaccurate projection from 2012 has been made by the tool. See https://github.com/colin-scott/interactive_latencies/issues/... .
comment by thundergolfer · 2022-03-04 · in How “latency numbers everybody should know” decreased from 1990–2020 -
Yes, this is a huge problem with the data for 2012 onwards. See: https://github.com/colin-scott/interactive_latencies/issues/... .
comment by thundergolfer · 2022-03-04 · in How “latency numbers everybody should know” decreased from 1990–2020 -
I was curious too, the network one is a TODO: https://github.com/colin-scott/interactive_latencies/blob/ma... Although I'd expect more jumps than Fast Ethernet to Gigabit, it's true the consumer space is kind of stuck on Gigabit (with 2.5…
comment by dgl · 2022-03-03 · in How “latency numbers everybody should know” decreased from 1990–2020 -
…a nanosecond or so, which leaves almost all of the latency budget for existential latency. edit: https://github.com/colin-scott/interactive_latencies/blob/ma... The data on this page is simply extrapolated using formulas and guesses.
comment by formerly_proven · 2022-03-03 · in How “latency numbers everybody should know” decreased from 1990–2020 -
…of the blocks so it's more useful going forward) Fwiw the "fork me on github" banner points to: https://github.com/colin-scott/interactive_latencies
comment by e12e · 2018-09-05 · in Latency Numbers Every Programmer Should Know -
…in the screen above). If you have any suggestions, a pull request would be much appreciated! https://github.com/colin-scott/interactive_latencies
comment by colin_scott · 2012-12-25 · in Latency Numbers Every Programmer Should Know -
…how I extrapolated. If you have any improvements to make, a pull request would be much appreciated! https://github.com/colin-scott/interactive_latencies
comment by colin_scott · 2012-12-25 · in Latency Numbers Every Programmer Should Know -
It's licensed under BSD: https://github.com/colin-scott/interactive_latencies Pull requests would be much appreciated!
comment by colin_scott · 2012-12-25 · in Latency Numbers Every Programmer Should Know