We halved DNS build delay and cut memory use by 85%
wondersky
171 points
69 comments
November 02, 2026
Related Discussions
Found 5 related stories in 110.8ms across 11,391 title embeddings via pgvector HNSW
- Saving 100 terabytes of memory by optimizing 1.1.1.1's DNS cache TangerineDream · 644 pts · August 27, 2026 · 71% similar
- Saving another 100TB of RAM f311a · 304 pts · September 18, 2026 · 58% similar
- We could save petabytes of cache storage with Zstandard and Pingora torutofu · 12 pts · September 01, 2026 · 57% similar
- HTTP/3 is faster with some work and help from Cloudflare saikatsg · 13 pts · October 31, 2026 · 52% similar
- Cloudflare AKE cuts origin HelloRetryRequests from 52% to 3.7% iamsyr · 102 pts · September 14, 2026 · 50% similar
Discussion Highlights (5 comments)
InsidiousWombat
Isn't 700 changes a second like... really low, considering their scale and amount of domains they manage ?
thephyber
I have been wondering if the memory scarcity would lead to a desire to optimize software to be more efficient. Curious what the R&D / efficiency development ROI is on reducing memory footprint. I suppose we should both consider current ROI and near future ROI (as the price of memory will likely stay high for at least another 1-2 years).
mhovd
Cloudflare doesn't get enough credit for their series of overall great technical blog posts.
JulianPaul
I'm very curious about the bugs (before vs. after relational) that come from an improvement like this over time
likoya
I used to use cloudflare dns, but the same cloudflare harassed me the entire day testing if I'm a robot. The harassment ended after I switched the dns server. See you never again, clouflare