<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Cloudflare freed up 100TB of RAM behind its 1.1.1.1 DNS without adding a single server — Live Feed</title><link>https://www.live-feeds.com/feed/cloudflare-freed-up-100tb-of-ram-behind-its-1-1-1-1-dns-without-adding-a-single-server</link><atom:link xmlns:atom="http://www.w3.org/2005/Atom" href="https://www.live-feeds.com/feed/cloudflare-freed-up-100tb-of-ram-behind-its-1-1-1-1-dns-without-adding-a-single-server/rss.xml" rel="self" type="application/rss+xml"/><description>Continuously updated, source-cited coverage.</description>
<item><title>Cloudflare recovers 100TB of RAM through 1.1.1.1 DNS cache optimization</title><link>https://www.live-feeds.com/feed/cloudflare-freed-up-100tb-of-ram-behind-its-1-1-1-1-dns-without-adding-a-single-server</link><guid isPermaLink="false">https://www.live-feeds.com/feed/cloudflare-freed-up-100tb-of-ram-behind-its-1-1-1-1-dns-without-adding-a-single-server#u53411</guid><pubDate>Tue, 01 Sep 2026 01:31:10 +0000</pubDate><description>Cloudflare reclaimed 100TB of memory across its fleet by redesigning the DNS cache for its 1.1.1.1 service. The company achieved this reduction without adding new servers by shrinking individual cache entries and implementing five specific optimizations. These changes halved the memory usage of the DNS cache. Because the system handles 250 billion cached DNS entries simultaneously, removing a single wasted byte from each entry results in a total saving of 250GB of RAM.Why it mattersDNS caches store IP address mappings to speed up internet requests. At the scale of 1.1.1.1, minor inefficiencies</description></item>
</channel></rss>