Skip to content
NewA calmer, faster ZeroHour

Cloudflare halves DNS build delay and cuts memory use 85%

Original title: How we halved DNS build delay and cut memory use by 85%

Cloudflare Blogby Alex Fattouche ()15 min read1
AI summary · x-ai/grok-4.7Summaries by Vani AI

A targeted planner skips full rebuilds of zones with tens of millions of records as changes rose from about 250 to 700 per second.

Cloudflare says its Zone Builder now receives about 700 DNS record changes per second, up from about 250 in 2022, plus about 100 other events. Some zones hold more than 20 million records. A planner that picks the smallest build it can prove safe, plus a scheduler that merges work for the same zone, cut peak memory 85% and halved time until changes are written to Quicksilver. Timestamp-only or unclear events still force a full build.

Key facts
  • On a one-million-record test zone in 2022, per-record builds were 4,250 times faster.
  • Zone setting changes no longer rebuild zones with tens of millions of records.
  • Events now include changed fields and previous and new values when available.
  • The planner refuses to do less work when a change is uncertain.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

15 min read at blog.cloudflare.com

Zone setting changes used to rebuild entire DNS zones, even ones with tens of millions of records. Here is how we built a planner that picks the smallest safe build, cutting full builds by 40%, peak memory by 85%, and halving build delay.

Cloudflare Blog

By Alex Fattouche · blog.cloudflare.com

Read the full article at Cloudflare Blog

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.