Reducing Network Latency: Innovations for a Faster Internet
summary
Live demonstration of TCP’s sawtooth and human “packets” shows why excessive buffering turns milliseconds into seconds — real-world records reached 864 seconds and fiber tests hit 3+ seconds. Presents concrete fixes: CAKE and fq_codel implemented in OpenWrt and Linux, deployed via SQM, plus L4S/ECN trials. Claims upgrades cut tail latency to ~20–38 ms across ~4 million devices, and Wi‑Fi tests reduce delay from ~1,400 ms down to tens of ms.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:53Where has the time gone?
- 3:03Got bufferbloat?
- 4:53What's congestion control?
- 6:31Other bufferbloat solutions
- 6:52Demo: Congestion control
- 11:51The TCP initial window
- 14:22TCP's slow start & congestion avoidance algos
- 15:24TCP Reno/Cubic sawtooth
- 17:23Receive & send windows
- 18:57The role of loss & marking
- 19:54Ack clocking
- 20:48Problem: Ridding the sawtooth
- 24:21Quiz
- 25:46Problem: Keeping queues short
- 29:29Cake vs Sonic fiber
- 30:52LCA 2020 WiFi network
- 31:10Outro
- 31:45Q&A
- 42:15Song
related talks
43mHow internet congestion control actually works in the bufferbloat age
26mTuning Your Cloud: Improve Global Network Performance for Applications
26mTuning Your Cloud: Improve Global Network Performance for Application
23mACK to the Future: TCP in 2025
23mThe Short and Happy Lives of TCP and HTTP Requests
24mResponsiveness Under Working Conditions
22mAdapting TCP for Reconfigurable Datacenter Networks
16m"Latency: Why You Should Worry and What You Can Do About It"
