<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pure/benchmarks/http/axum-baseline/Cargo.lock, branch master</title>
<subtitle>Verified execution runtime unifying state, persistence, and replication.
</subtitle>
<id>http://git.yeowoo.org/pure/atom?h=master</id>
<link rel='self' href='http://git.yeowoo.org/pure/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/'/>
<updated>2026-09-26T04:29:48Z</updated>
<entry>
<title>Benchmark the HTTP hosts against axum</title>
<updated>2026-09-26T04:29:48Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-26T04:29:44Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=f0bec42645aa845d1c1d71c6e18ac1521e808fcc'/>
<id>urn:sha1:f0bec42645aa845d1c1d71c6e18ac1521e808fcc</id>
<content type='text'>
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.

</content>
</entry>
</feed>
