Metraipolis › archive › dc_224fa9d93055

Throughput per Megabyte: A Pilot Benchmark of Language-Stack Efficiency for Self-Hosted HTTP Services on a Raspberry Pi 5 — arXiv:2609.11932

Source
arXiv (en)
Original
https://arxiv.org/abs/2609.11932
License (as archived)
CC0-1.0
Archived
2026-10-16T03:08:38.372Z
SHA-256 of the archived text
e130853649c5a6b931ad81ff6d32a2c14af971eeb3823a92d210079f7683f9e5
Stable URL of this page
https://metraipolis.com/documento/dc_224fa9d93055

How to cite

Throughput per Megabyte: A Pilot Benchmark of Language-Stack Efficiency for Self-Hosted HTTP Services on a Raspberry Pi 5 — arXiv:2609.11932 — arXiv (en), https://arxiv.org/abs/2609.11932 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_224fa9d93055 (Metraipolis archive dc_224fa9d93055, sha256 e130853649c5a6b931ad81ff6d32a2c14af971eeb3823a92d210079f7683f9e5)
BibTeX
@misc{dc224fa9d93055,
  title = {Throughput per Megabyte: A Pilot Benchmark of Language-Stack Efficiency for Self-Hosted HTTP Services on a Raspberry Pi 5 — arXiv:2609.11932},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2609.11932},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_224fa9d93055; sha256 e130853649c5a6b931ad81ff6d32a2c14af971eeb3823a92d210079f7683f9e5},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.11932. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

Cloud-centric web benchmarks miss constraints that matter for self-hosted services on ARM64 single-board computers, especially idle RAM footprint and energy per request. We ran a pilot benchmark on one Raspberry Pi 5, measuring equivalent SQLite-backed CRUD APIs implemented in Go 1.26/net/http, Rust 1.95/Axum, Python 3.13/FastAPI+Granian, this http URL 24/Fastify, and .NET 10 Native AOT across N=50 randomized runs per stack and endpoint, with a separate concurrency sweep and memory time-series collection. Rust achieved the highest weighted throughput-to-RAM ratio (310.25 req/s/MB, 2.8x Go) because its weighted peak RSS was 7.36 MB, while .NET, this http URL , Go, and Rust formed a raw-throughput cluster with overlapping bootstrap CIs (2,125--2,461 req/s) and Python remained below that cluster at 969 req/s. The concurrency sweep on GET /items/:id showed divergent scaling: .NET reached 26,209 req/s at c=240, Go and Rust plateaued near c=120, this http URL saturated near 9,700 req/s, and Python stayed below 2,300 req/s; memory snapshots showed Rust holding a flat 7.8 MB RSS while this http URL grew by 117 MB without visible GC drops. For RAM-constrained self-hosted CRUD-over-SQLite deployments on this Pi 5 unit, the data support Rust as the most resource-efficient measured stack, .NET as the strongest high-concurrency stack, and Go as a practical option where ecosystem breadth matters; replication is needed before extending these findings to other devices or storage backends.

Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-14 in cs.DC).
Categorie arXiv: Performance (cs.PF) ; Distributed, Parallel, and Cluster Computing (cs.DC); Programming Languages (cs.PL).
Pagina del lavoro: https://arxiv.org/abs/2609.11932 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-16T03:03:05.092Z dalla pagina https://arxiv.org/catchup/cs.DC/2026-09-14?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).