The revenge of the listening sockets
Back in November we wrote a blog post about one latency spike. Today I'd like to share a continuation of that story. As it turns out, the misconfigured rmem setting wasn't the only source of added latency. It looked like Mr Wolf hadn't finished his job.
Discussion around the web
- Hacker News388 · 60 💬
Score breakdown
- Technical depth91
- Practical value45
- Originality60
- Writing quality96
- Source reputation90
- Recency0
- External engagement35
- On-site engagement0
More like this
Discord Engineering46
How Discord Supercharges Network Disks for Extreme Low Latency
unknown·16 min read
Slack Engineering60
Tracing at Slack: Thinking in Causal Graphs
unknown·18 min read
The GitHub Blog63
Debugging network stalls on Kubernetes
Theo Julienne·unknown·26 min read
Dropbox Tech57
Investigating the impact of HTTP3 on network latency for search
Tiffany Fong·unknown·8 min read
Engradar shows a summary and links to the original article. The full article is hosted on blog.cloudflare.com.