From 313c4fa1720a0019c87083d3523b6643606c5aa6 Mon Sep 17 00:00:00 2001 From: eunhhu Date: Sun, 27 Sep 2026 19:11:45 +0100 Subject: Record the small reads and idle memory work, next to axum and drogon (087) What the app model, snapshot reads and delivery had cost small reads (126.7k -> 116.1k GETs a second) and idle memory (2.0 -> 4.5 MiB), how the sampler found it, and the four steps and the crypto split that took it back: 139.9k and 2.3 MiB. Measured again today beside axum 0.8.9 and drogon 1.9.0 on the same Pi: a one-thread pure-serve answers small GETs at 139k/s (2.2x axum and drogon a CPU second), 1 MiB GETs at 2,362/s (axum 1,304, drogon 754), durable app writes at 21.3k/s (both about 200), with the least idle memory of the three. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 9762cc9..4aa46ba 100644 --- a/README.md +++ b/README.md @@ -11,8 +11,8 @@ batches, and a receiving app applies each message once; sealed to the receiver's them can read or change it. Measurements against axum and drogon on a Raspberry Pi 5 are in [075](docs/research/075-http-host-against-axum.md), [077](docs/research/077-apps-as-http-services.md), [080](docs/research/080-snapshot-reads.md), [081](docs/research/081-tail-records.md), -[082](docs/research/082-json-in-place.md), [083](docs/research/083-delivery-over-http.md) and -[086](docs/research/086-sealed-sends.md); the status table is +[082](docs/research/082-json-in-place.md), [083](docs/research/083-delivery-over-http.md), +[086](docs/research/086-sealed-sends.md) and [087](docs/research/087-small-reads-and-idle-memory.md); the status table is [CHECKPOINT.md](CHECKPOINT.md). The source follows the principle below, a small core with the rest selected around it -- cgit v1.2.3