← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Cloudflare's 1.1.1.1 DNS service optimizes cache, saving 100TB memory

🔄 Updated 2h ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Cloudflare optimized DNS cache entry storage for 1.1.1.1.
  • Five changes reduced memory footprint by over 50%.
  • 100 terabytes of memory were saved across the fleet.
  • Cache insert throughput increased 43%, lookup latency dropped 19%.

DNS Cache Optimization

Cloudflare's Big Pineapple platform, responsible for services like 1.1.1.1 DNS, implemented five successive changes to how it stores DNS cache entries in memory. This platform manages over 250 billion DNS cache entries at any given time, making memory efficiency critical.

Memory and Performance Gains

The optimizations resulted in a reduction of the per-entry memory footprint by over 50%. This translated to approximately 100 terabytes of memory freed across Cloudflare's server fleet, equivalent to the RAM in 130 Gen 13 servers. Beyond memory savings, the cache also saw performance improvements, with insert throughput increasing by 43% and lookup latency decreasing by 19%.

Caching Mechanism

The cache starts empty and fills as DNS queries arrive, evicting older or less popular items when it reaches its maximum capacity. Cache size varies by data center, especially with EDNS Client Subnet (ECS) in use, which can increase the number of entries and memory consumption due to caching multiple versions of the same query. Each cache item is a key-value pair, where the key identifies the query (qname, qtype, authenticated, tag) and the value stores the DNS response along with metadata like timestamp, TTL, and hit count.

Benchmarking Methodology

To measure the impact of each change, Cloudflare benchmarked memory usage by filling the cache with randomly generated entries. These entries mimicked production traffic distribution, consisting of 56% A records, 25% AAAA records, and 19% TXT records, with each entry containing between one and four records. TXT records served as a stand-in for other variable-length record types, with sizes randomized between 64 and 224 bytes.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~20 min · 17 stories · Aug 27

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Cloudflare's Big Pineapple platform, which powers the 1.1.1.1 DNS service, implemented five changes to its DNS cache entry storage. These optimizations reduced the per-entry memory footprint by over 50%, freeing up approximately 100 terabytes of memory across its fleet and improving cache performance.