Urgent.News

What's breaking now, across thousands of outlets.

Tech

Cloudflare freed up 100TB of RAM behind its 1.1.1.1 DNS without adding a single server

The optimization work was centered on Big Pineapple, Cloudflare's DNS caching platform behind the popular 1.1.1.1 resolver, DNS Firewall, and several other DNS services they offer. In a technical blog post, systems engineer Sebastiaan Neuteboom detailed five changes to the Rust codebase that shrank a typical cache entry from 953... Read Entire Article

Cloudflare freed up 100TB of RAM behind its 1.1.1.1 DNS without adding a single server

Cloudflare has successfully reduced the memory usage of its DNS cache, behind its popular resolver 1.1.1.1, by over half, freeing approximately 100TB of RAM across its network. The memory optimization was achieved by altering the software that stores cached DNS data within the Big Pineapple platform, which powers DNS services such as the DNS Firewall.

A detailed technical blog post by systems engineer Sebastiaan Neuteboom outlined five code changes in the Rust programming language that shrank cache entries from 953 bytes to 420 bytes, while also improving cache performance. Cache insert throughput increased from 625,000 to 893,000 entries per second, and lookup latency decreased from 828 nanoseconds to 670 nanoseconds.

During the rollout from mid-May to early July, p99 memory usage per instance dropped from 9.3GB to 5.3GB. Big Pineapple manages more than 250 billion DNS entries, and even minor memory waste adds up quickly. Cloudflare estimates that one unnecessary byte in a cache entry costs more than 250GB across its entire fleet. The company replaced Rust's Vec and String types with fixed-size boxed slices, eliminating unnecessary metadata, which alone saved over 15TB of RAM.

Additionally, Big Pineapple now stores DNS records as length-prefixed raw wire-format bytes, addressing a memory waste issue caused by a mismatch between record sizes. With the 100TB of reclaimed RAM, Cloudflare intends to allocate more memory to larger DNS caches, improving cache hit rates and reducing traffic to authoritative DNS servers.

This memory efficiency project builds on Cloudflare's previous effort to rewrite its FL2 request-handling layer in Rust, further demonstrating the company's commitment to optimizing its existing infrastructure as server memory costs rise.

Written by urgent.news from TechSpot's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at techspot.com →

More in Tech

Four pull requests, four full suites, one answer

While the project was small, none of this mattered. It grew, and the suite grew with it. A great many tests need a great deal of machine time, and that becomes a choice where both answers cost: run…

  • Merge queue runs full suite per batch, not per pull request
  • Merge queue still runs full suite once per pull request in group
  • Subset of tests is only way to avoid running full suite

POO: Classes Concretas

Introdução Uma classe é concreta quando está 100% implementada. Nenhum membro fica pendurado sem corpo. É por isso, e so por isso que o compilador libera o new .

  • Concrete classes fully implemented without abstract members
  • Allow 'new' usage for concrete classes in compilation
  • Contain private fields, read-only properties, static members

More from Saturday 29 August →