The story of one latency spike
Nov 19, 2015Marek Majkowski

Summary
This post details the investigation and resolution of rare, significant latency spikes experienced by a customer. It showcases the use of advanced debugging tools like System Tap and flame graphs to pinpoint the root cause within the Linux kernel's `tcp_collapse` function, which was exacerbated by large TCP receive buffer sizes. The post demonstrates how tuning the `net.ipv4.tcp_rmem` sysctl parameter significantly improved network performance and stability, highlighting Cloudflare's commitment to deep system-level performance optimization.
More from the Data Infrastructure & Analytics trail
- Introducing Cloudflare Basin: an open, serverless data platform, now generally available
- Introducing the Billable Usage API: programmatic cost visibility for Cloudflare
- Announcing the Monetization Gateway: charge for any resource behind Cloudflare via x402
- How we built Cloudflare's data platform and an AI agent on top of it
- Iran's Internet is partially restored, Cloudflare Radar data shows