letloop is an async runtime for Scheme, built on Chez Scheme, the pico HTTP parser and io_uring.
You write ordinary Scheme. The runtime schedules I/O through io_uring
underneath. There is no function coloring, no await
keyword, no split between “async code” and “normal code”: a procedure
that reads from a socket and one that computes a factorial share the
same calling convention, the same continuation model and the same
debugging tools.
On a trivial counter endpoint, single-threaded, letloop (flow2 + io_uring) peaks at 305,820 req/s (16 connections) with a p99 of 0.083ms, and still serves 233,948 req/s at 256 connections. That places second of 6 HTTP server implementations, behind only Rust (axum + tokio) at 407,045 req/s and ahead of Bun (canary) at 302,935 req/s, Bun at 294,188 req/s, Node.js at 192,297 req/s and FastAPI (uvicorn) at 36,096 req/s. These are micro-benchmarks: they show raw I/O throughput and nothing else.
Work in progress. The scheduler is single-threaded and the error handling story is incomplete.