This article details Cloudflare's Gen 13 server hardware design, emphasizing how component selection for CPU, memory, and storage directly supports their Rust-based FL2 request handling layer. It highlights the architectural decisions and trade-offs made to achieve significant throughput, performance-per-watt, and operational efficiency gains crucial for a global distributed network.
Read original on Cloudflare BlogCloudflare's transition to its Rust-based FL2 request handling layer necessitated a complete refresh of its server hardware, culminating in the Gen 13 design. This redesign exemplifies how software architecture deeply influences hardware choices in large-scale distributed systems, driving optimizations for throughput, efficiency, and operational simplicity. The core principle was to align hardware capabilities with the evolving demands of a high-performance network.
The choice of AMD EPYC™ Turin 9965 (192-core) over other Turin candidates demonstrates a critical architectural trade-off. While it has less L3 cache per core than previous generations, the FL2 workload's low L3 cache dependency and high core count scalability made the 9965 the optimal choice for achieving significant throughput gains and better performance-per-watt. This decision underscores that raw specifications are less important than how they match specific software workload characteristics.
| Feature | Gen 12 (AMD Genoa-X 9684X) | Gen 13 (AMD Turin 9965) |
|---|
Software-Hardware Co-Design
The alignment between software (FL2's Rust-based architecture) and hardware (high core count, lower L3 cache per core) is a crucial lesson. System designers must understand workload profiles to make informed hardware decisions, rather than blindly pursuing higher individual component specs.