pure/benchmarks/http/axum-baseline/src/main.rs, branch masterVerified execution runtime unifying state, persistence, and replication.
http://git.yeowoo.org/pure/atom?h=master2026-09-26T15:56:08ZBenchmark an app served by its views and inputs2026-09-26T15:56:08Zeunhhunecpition205@gmail.com2026-09-26T15:56:08Zurn:sha1:768317d789a01d722fe7455d792fed11e6579b5c
run.py --suite app serves the scoreboard of scores.aup (22 lines of aup)
with pure-serve against the same scoreboard written by hand in axum and
drogon: POST /inputs/score?points=N with a name as the body, GET
/views/total and a page of 20 rows as JSON. Durable, the baselines append
each score to a log and fdatasync it before answering (replayed at
start); the load generator learns the three requests.
Benchmark the HTTP hosts against axum2026-09-26T04:29:48Zeunhhunecpition205@gmail.com2026-09-26T04:29:44Zurn:sha1:f0bec42645aa845d1c1d71c6e18ac1521e808fcc
A C load generator, an axum service with the same document contract (in
memory, fdatasync, and crash-safe replacement), and a runner that pins the
servers and the load to separate CPUs. On the Pi 5, Pure uses about 40%
less memory, wins with a new connection per request and with eight durable
writers (3.2x the crash-safe axum), but loses 5x on keep-alive reads and
1.5x on 64 durable writers: no persistent connections, one thread, eight
connection slots and two fsyncs per commit. Note 075 records the numbers
and the targets.