proomt

Search

Search posts, papers, and topics

All posts

TailscaleKabir Sikand, Kevin Purdy7 min readintermediate

We're making Tailscale faster

Summary

Tailscale is cutting memory overhead for small packets, adding a multi‑queue pipeline for routers and exit nodes, using Linux’s writev, and introducing netmap caching to speed up startup. These changes give ~5 % throughput gains now and larger gains in upcoming releases.

  • On Linux/Android Tailscale now reuses a single 64 KiB read buffer for many small packets, avoiding per‑packet copies and reducing memory use, yielding ~5 % throughput improvement.
  • A new multi‑queue architecture assigns each traffic flow its own lane, allowing parallel processing across CPU cores for subnet routers, app connectors, and exit nodes, improving aggregate capacity and latency.
  • Tailscale now uses the Linux writev system call to send packet fragments to the kernel in a single operation, cutting memory copies and boosting throughput.
  • Netmap caching stores the control‑plane network map on disk so clients can start communicating before the control plane is reachable, reducing startup latency by up to two orders of magnitude in poor‑network scenarios.

Reducing per‑packet memory copies and enabling parallel packet processing directly translates to higher bandwidth and lower latency for Tailscale‑based workloads such as CI pipelines, remote development, and edge devices, making a mesh VPN viable for performance‑sensitive applications.

6/10

Related reading

  1. The Tail at Scale

    The paper defines “tail‑tolerant” systems that keep interactive latency (≤100 ms) low even as services scale to thousands of servers, and surveys the main causes of latency outliers. It shows that techniques such as request replication, hedged requests, and resource isolation can dramatically shrink the latency tail with modest overhead, enabling higher utilization without over‑provisioning.

    Hall of Fameresearch.google1 minpaper
  2. The TailscaleUp-date

    Tailscale announced new features at its upcoming TailscaleUp event, including AI gateway Aperture enhancements, time‑bound privileged access, DNS‑level protection, and richer programmable APIs. These aim to give teams finer identity‑based control over access to internal and cloud resources.

    Tailscaletailscale.com3 min
  3. 1 points

    Saving another 100TB of RAM with math (and Rust)

    Cloudflare reduced the memory footprint of its Pingora Backend Router by re‑examining the consistent‑hashing implementation in the pingora‑ketama library. By increasing the number of virtual hash points per server from the default 1 to the standard 160 (and applying weighted hashing based on disk capacity), they cut the per‑node overhead enough to reclaim >100 TB of RAM across the fleet. The post…

    Hacker News front pagecloudflare.com13 minHN478120lobste.rs33
  4. Faster Maps: Chasing Swiss Speed

    ParparVM’s HashMap suffered catastrophic miss latency due to linear probing on dense integer keys. By adopting CPython‑style perturbed probing (Swiss‑table style) and extending tagged immediate values to more primitives, miss latency dropped from 32 s to ~45 ms, allocation pressure fell dramatically, and overall performance stayed roughly flat despite a modest hit‑time slowdown.

    CodeName Onecodenameone.com8 min
  5. Aperture GA: Building a home(lab) for agentic AI

    Aperture, Tailscale’s AI gateway, is now generally available. It ships with starter tokens, in‑app token purchases, new Model Context Protocol (MCP) endpoints for adding Tailnet nodes and invoking Tailscale SSH, and an upgraded chat UI that supports Projects (shared context, tool access, node groups) and configurable default tool permissions. All agent actions respect Tailscale’s unidirectional A…

    Tailscaletailscale.com4 minreleaseHN41