Reading up on 1.1.1.1
3 deep · digging since jan 22
- Saving 100 terabytes of memory by optimizing 1.1.1.1's DNS cache
Cloudflare cut over 100 terabytes of RAM used by its 1.1.1.1 DNS cache by redesigning cache layout and eviction policies without hurting query latency.
- How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache
Cloudflare reduced its Big Pineapple DNS cache entry size by 56% through five Rust optimizations, freeing ~100 TB of memory while boosting insert throughput 43% and cutting lookup latency 19%.
- What came first: the CNAME or the A record?
Cloudflare's reordering of CNAME records in DNS responses broke glibc and other clients due to widespread reliance on undocumented ordering.