Caddy compatibility for zeroserve: 3x throughput and 70% lower latency

# Caddy compatibility for zeroserve: 3x throughput and 70% lower latency Source: [https://su3.io/posts/zeroserve-caddy-compat](https://su3.io/posts/zeroserve-caddy-compat) [zeroserve](https://github.com/losfair/zeroserve)is a high\-performance HTTPS server that runs eBPF scripts in userspace \([intro](https://su3.io/posts/introducing-zeroserve)\)\. Now it's got a Caddy\-compat mode \- when provided a Caddyfile, zeroserve JIT\-compiles it to eBPF and then to native x86\_64/ARM64 machine code, and runs it in an`io\_uring`event loop\. protocolserverthroughputp50p99peak RSShttpszeroserve\-clang38,948 req/s1\.45ms3\.91ms30\.9 MiBhttpszeroserve\-tcc36,653 req/s1\.67ms4\.00ms34\.2 MiBhttpscaddy12,529 req/s4\.74ms13\.11ms67\.4 MiBhttpsnginx37,424 req/s1\.57ms4\.24ms25\.7 MiB*HTTPS reverse proxy, 2 threads, AMD Ryzen 7 3700X\.**[Check CI](https://github.com/losfair/zeroserve/actions/runs/27498328347/job/81276438772)**for original run result\.* Try it with your Caddyfile: ``` curl -fL -o zeroserve https://github.com/losfair/zeroserve/releases/download/v0.2.11/zeroserve-$(uname -m)-linux chmod +x zeroserve ./zeroserve --caddy /etc/caddy/Caddyfile curl http://127.0.0.1:8080 ``` zeroserve runs turing\-complete eBPF and you can call custom code from your Caddyfile\. For example, to reverse\-proxy a path to an S3\-compatible bucket with AWS SigV4 auth, grab[io\.su3\.aws\-sigv4\.c](https://github.com/losfair/zeroserve/blob/main/plugins/io.su3.aws-sigv4.c)and then: ``` # zeroserve --plugin io.su3.aws-sigv4.c --caddy Caddyfile example.com { route /s3/* { uri strip_prefix /s3 rewrite * /my-bucket{uri} # Call the `sign_request` method in the eBPF middleware `io.su3.aws-sigv4.o` zeroserve_call io.su3.aws-sigv4 sign_request { access_key_id "minioadmin" secret_access_key "minioadmin" } reverse_proxy http://127.0.0.1:9000 } } ``` © 2022\-2026 Heyang Zhou · [RSS](https://su3.io/api/feed)