Cloudflare Redesigns Edge Stack for 192-Core CPUs, Ditches Shared Cache Model

Cloudflare's Gen 13 servers pack 192 cores per box, but the cache-per-core ratio drops relative to older generations. Rather than fight the hardware constraint, they redesigned their software around shared-nothing architecture: each core gets its own connection tables, routing state, and buffer pools, with no cross-core locking. Connections pin to specific cores via receive-side scaling, eliminating cache thrashing and coordination overhead. This mirrors patterns used in Seastar and DPDK stacks, but Cloudflare is applying it across their entire edge network—HTTP, DNS, TLS, Workers, DDoS mitigation. The operational payoff should be tighter latency tails under load and higher edge compute density per rack unit, though they haven't published concrete before-and-after numbers. The engineering surface area for a migration this broad is substantial. The story is substantive technical work, not marketing. Cloudflare's own engineering blog provides the detail; InfoQ summarizes it competently. Worth reading if you operate edge infrastructure or care how constraint-driven architecture decisions actually get made. https://www.infoq.com/news/2026/04/cache-parallelism-cloudflare/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global