Weekly Digest // WEB_DEV_GENERAL — Week 35-2026
folder_openWeekly Report

Cloudflare Cuts 100 TB from a DNS Cache — Week 35 Web Development

Cloudflare memory work, faster browser releases, and a failed CDN cache show why optimization begins with population, locality, and break-even math.

calendar_todaysummarizeWeek 35-2026
TAG: SYSTEMS PERFORMANCEREAD_TIME: 11_MIN

How Cloudflare Saved 100 TB of DNS Cache Memory

Cloudflare's cache holds more than 250 billion DNS entries, so one wasted byte costs over 250 GB across the fleet. Five representation changes cut an entry from 953 to 420 bytes and freed roughly 100 TB: immutable boxes replace growable vectors, sections share one list, repeated record owners disappear, large enum variants move out of line, and encoded record data becomes contiguous. Insert throughput rose from 625,000 to 893,000 entries per second while lookup latency fell from 828 ns to 670 ns.

TAG: WEB PERFORMANCEREAD_TIME: 5_MIN

Faster Browser Releases Change Your RUM Population

Chrome and Firefox are preparing two-week major release cycles, so exact-version cohorts will become smaller and more transient. A 28-day RUM window can span multiple milestones even when the site does not deploy, while Extended Stable retains a separate long-lived population. Harry Roberts recommends release annotations, minimum sample thresholds, Beta journey testing, and an unsegmented user view. His related navigation study found 7,131,737 unattributed-overhead observations beside only 166 visible redirects.

TAG: CACHE ECONOMICSREAD_TIME: 7_MIN

When a CDN Cache Makes a Site Slower

A static site's warm cache hit reached 0.239 seconds, but a cold miss cost 0.366 seconds against a 0.281-second uncached baseline. The break-even equation required a 67% hit rate. With about nine daily visitors spread over 77 pages, many edge locations, and deploy purges, the realistic rate was near zero; an external crawler's slow-page count rose from 38 to 75. The failure shows why teams must measure hits, misses, and the original user-facing metric before treating “cached” as synonymous with “faster.”

summarizeDigest_Summary

Cloudflare reduced the per-entry footprint of a cache holding more than 250 billion DNS entries from 953 bytes to 420 bytes. Replacing growable collections, packing flags, removing repeated owners, and storing record data contiguously freed roughly 100 terabytes across the fleet. Insert throughput rose 43% and lookup latency fell 19%, showing how fewer allocations and better locality can improve both capacity and speed.

Chrome and Firefox are moving toward two-week major release cycles, which means browser-version mix can shift real-user monitoring without an application deploy. Smaller cohorts, more boundaries inside a 28-day window, and long-lived managed releases can all move a percentile. One navigation study also found 7,131,737 observations with unattributed overhead beside only 166 visible redirects, reinforcing the need to name missing time without pretending the remainder is already diagnosed.

A small static site's CDN experiment supplies the break-even check. Warm hits reached 0.239 seconds, cold misses cost 0.366 seconds, and the uncached baseline was 0.281 seconds; caching therefore needed a 67% hit rate merely to break even. With nine daily visitors spread across 77 pages and many edge locations, the real hit rate approached zero and a crawler's slow-page count rose from 38 to 75.

Key Takeaways
  • Profile the representation before scaling hardware: immutable data can often drop capacity fields, repeated values, large inline enum variants, and scattered allocations.
  • Annotate browser Beta and Stable dates in RUM, retain an overall user view, and require minimum samples before treating exact-version percentiles as explanations.
  • Measure cache hit, miss, and uncached latency from user locations, calculate the break-even hit rate, and verify against the metric that originally exposed the problem.