# Cloudflare launches Gen 13 edge servers with Turin CPUs and FL2 > Cloudflare’s Gen 13 design pairs 192-core AMD Turin processors with its Rust-based FL2 request layer to double edge throughput in testing. Canonical URL: https://www.devobs.io/news/news-cloudflare-gen13-edge-servers-fl2/ By: Samira Haddad Published: 2026-09-06T11:58:54.639Z Updated: 2026-09-06T11:58:54.639Z Event date: 2026-03-23 Section: Infrastructure Cloudflare launched its Gen 13 edge server platform on March 23, pairing AMD EPYC 9965 Turin processors with FL2, its Rust-based request-handling layer. The [engineering announcement](https://blog.cloudflare.com/gen13-launch/) says hardware qualification is complete and servers are shipping at scale for a global rollout. ## More cores required a different software profile The selected processor has 192 cores, twice Gen 12’s 96, but much less L3 cache per core. Cloudflare’s older FL1 stack was sensitive to that tradeoff: higher core density increased potential throughput while cache pressure threatened latency targets. FL2’s leaner memory-access pattern reduced that dependency and let throughput scale with the additional cores. Cloudflare reports that the Gen 13 configuration delivered up to twice Gen 12’s request throughput, up to 50% better performance per watt, and 60% greater rack throughput within the same rack power budget. These are Cloudflare’s fleet qualification results for its serving workload, not general benchmarks for every application using the same processor. ## Hardware and software were one capacity decision The launch is a useful example of testing the entire service path before selecting a server generation. A CPU with a stronger headline core count can underperform if a hot path depends on cache behavior that the new design changes. Conversely, a software rewrite can alter which hardware tradeoffs are acceptable. Infrastructure teams making a similar transition should benchmark production-shaped request mixes, enforce latency objectives during load tests, and measure power at the rack rather than only at the socket. Rollout plans should preserve a comparison cohort and a rollback path. Cloudflare’s result came from co-design and staged production measurement; the transferable lesson is the method, not the exact percentage gain. ## Source references -