computer-science
Caddy compatibility for zeroserve: 3x throughput and 70% lower latency
Key takeaways
- Now it's got a Caddy-compat mode - when provided a Caddyfile, zeroserve JIT-compiles it to e BPF and then to native x86_64/ARM64 machine code, and runs it in an io_uringevent loop.
- HTTPS reverse proxy, 2 threads, AMD Ryzen 7 3700X.
- For example, to reverse-proxy a path to an S3-compatible bucket with AWS SigV4 auth, grab io.su3.aws-sigv4.c and then:
Now it's got a Caddy-compat mode - when provided a Caddyfile, zeroserve JIT-compiles it to e BPF and then to native x86_64/ARM64 machine code, and runs it in an io_uringevent loop.
HTTPS reverse proxy, 2 threads, AMD Ryzen 7 3700X. Check CI for original run result.
curl -f L -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 and then:
Article preview — originally published by Hacker News. Full story at the source.
Read full story on Hacker News →
More top stories
Aggregated and edited by the Scoop newsroom. We surface news from Hacker News alongside other reporting so you can compare coverage in one place.
Editorial policy · Corrections · About Scoop