News › performance
By The Linux Camp News, October 27, 2026
Beeper lets hyper-fast-path parse HTTP and serve static assets inside the kernel. The author's 4.5× result is for local HTTP/2 traffic and a 32KB asset, not a general web-server speedup.
The hyper-fast-path project, highlighted by Phoronix on October 27, 2026, reports up to 4.5× maximum throughput against an axum server when serving a 32KB static asset. It uses Beeper to parse HTTP/1.1 and HTTP/2 inside the Linux kernel and serve static requests there. This is a project-specific acceleration path for Hyper, not an announced performance improvement for Linux web servers generally; October 27 is the coverage date, not an established project release date. 1 3
Beeper makes application-layer parsing suitable for eBPF by constructing an Aho-Corasick-like deterministic finite automaton, or DFA, in user space. A DFA represents parsing as transitions between defined states. Preparing that machinery outside the kernel reduces the complexity of the parsing performed inside it. Beeper can then inspect application traffic and respond directly from the kernel; hyper-fast-path applies that capability to static assets. The important change is where those requests can be handled, rather than simply replacing one user-space HTTP parser with another. 2 3
The author's results distinguish local from remote traffic. Maximum throughput was 4.3× the axum baseline for local HTTP/1.1 and 4.5× for local HTTP/2, versus 3× and 3.4× respectively for remote traffic. At 2,000 requests per second, reported latency fell 54% for local HTTP/1.1, 53% for local HTTP/2 and 44% for both remote cases. Those latency figures describe a fixed request rate, not latency at maximum throughput. These are project-author measurements, not an independent reproduction. 3
The baseline also matters: Hyper is a low-level HTTP building block, and axum is built on it. Axum's own documentation describes its overhead above Hyper as small. The comparison therefore should not be read as evidence that swapping axum for ordinary Hyper delivers the reported multiplier. The tested alternative adds an in-kernel static-serving path. 4 5 3
For an evaluation, first check compatibility: Beeper's documentation retrieved October 27, 2026 lists Linux 6.8 as the minimum kernel for both HTTP parsers. The project provides separate local and remote benchmark scripts using oha on the load-generating machine. Its example also documents a server-log indication that a request was served directly from the kernel. That indication checks whether the demonstrated path was exercised; it does not establish a throughput gain. 2 3
Use representative asset sizes, request rates and traffic placement before drawing a capacity-planning conclusion. The author explicitly says performance depends heavily on those variables and that the benchmark covers only static assets. Consequently, gains for dynamic application handlers remain unestablished by this test, and the 4.5× local result is not a supported expectation for a remote production workload. 3