Proa benchmarks

Proa renders typed Rust components to HTML on the server, streams them, and hydrates fine-grained browser islands. This page shows what one core serves over HTTP, how fast seventeen renderers render those pages, and how to reproduce them.

If you see an issue with the benchmarks or would like to add any, please open an issue!

Reproducing a capture

Install the JavaScript dependencies once. You need Node.js 24.20.0 exactly — the canonical runner compares process.version and refuses to run on anything else — with pnpm, the Rust toolchain in rust-toolchain.toml, and Go 1.25. The full scoreboard also needs Ruby 3.2+, a JDK 17+ with Gradle, PHP 8, and Python 3.13+.

pnpm install --frozen-lockfile
pnpm exec playwright install chromium
npm ci --prefix rendering/external/react
npm ci --prefix rendering/external/marko
npm ci --prefix rendering/external/handlebars

Then run a suite. Each command builds its servers, gates every page for parity, and rewrites its evidence page. It refuses to publish a phase whose load generator was the bottleneck.

./rendering/run-all            # scoreboard: build, parity-gate, time, regenerate scoreboard.md
pnpm run bench:page-load       # canonical pages over HTTP, one core each
pnpm run bench:cold-start      # cold start to first response
pnpm run bench:suspense-load   # Suspense streaming over HTTP
pnpm run refresh               # regenerate every evidence page and figure from the captures

Good to know: the committed numbers are dated evidence from one machine, not universal claims. Rerun the relevant suite before publishing a current comparison.

Next steps

• HTTP capacity, cold start and streaming
  • Sustained responses per second, CPU per response, latency at equal load, and cold start for four production servers.
• Canonical scoreboard evidence
  • The seventeen-renderer table, parity coverage, every retained percentile, and the adapters side by side.
• Engineering, application and agent captures
  • Product-grid scaling, the memcpy floor, Proa's buffer allocation, client JavaScript, and the archived August report.
• Benchmark figures
  • How every SVG is drawn from the evidence pages' own tables and checked against them.
• Canonical benchmark protocol
  • The fairness rules, workload shapes, and parity gate in full.
• Suite READMEs: rendering/, page-load/, suspense-load/, load/, showcase/, agent-chain/, and the separate travel-agent/ control.

License and attribution

This repository is Apache-2.0; see LICENSE. Benchmark adapters incorporate upstream work under its own terms, recorded in rendering/UPSTREAM_LICENSES.md.

React, Marko, Vue, Svelte, Rails, jte, Rocker, Handlebars, Go, Jinja2, PHP, Askama, Sailfish, Leptos, Dioxus, and Topcoat belong to their respective owners. They appear here as the subjects of a benchmark; their inclusion implies no endorsement.