How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache
First reported · 58d ago · 2 sources
Crest summary — written by AI from the 2 sources below; every figure is checked against them · model deepseek-chat
Summary
Cloudflare reduced memory use in its 1.1.1.1 DNS cache through five Rust-level optimizations to the cache layout, cutting per-entry memory by 56% and freeing roughly 100 TB across its fleet.
Key facts
- Cloudflare applied five Rust-level memory optimizations to the 1.1.1.1 DNS cache layout.
- Per-entry memory dropped 56%, freeing about 100 TB fleet-wide.
- The work was detailed on the Cloudflare Blog on 2026-08-27.
Why it matters
Freeing roughly 100 TB of memory across a DNS fleet lowers the hardware footprint needed to serve the same query volume, which can reduce infrastructure cost for operators running large-scale DNS or caching systems.
Companies
Technologies
- Rustlanguage
- 1.1.1.1service
- Big Pineappleproduct
Related on Crest
Matched by rule, not by AI: a repository linked in the coverage, or a technology or company in this event that Crest tracks.
Repositories
Original sources (2)
The 2 reports this event was built from. Crest of Tech keeps no article bodies: the full text is at each source.
- Cloudflare BlogOfficial · PrimaryHow we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache · By Sebastiaan NeuteboomRead at Cloudflare Blog
- Hacker NewsCommunitySaving 100 terabytes of memory by optimizing 1.1.1.1's DNS cache · By TangerineDreamRead at Hacker News