Skip to content

About

SSR benchmarks for web frameworks and template engines. Compare server-side rendering, HTTP throughput, streaming, cold starts and memory usage with reproducible workloads.

Topics

Resources

Contributing

Stars

7 stars

Watchers

0 watching

Forks

Repository files navigation

SSR benchmarks for web frameworks

Reproducible server-side rendering (SSR) benchmarks and web framework benchmarks for comparing rendering time, HTTP throughput, streaming latency, cold starts and memory usage. We render shared pages across frameworks and template engines, check their output, and publish the code, pinned versions and raw measurements.

Explore the benchmark results and feature comparison → frameworks.run

Frameworks and renderers

The SSR Rendering suite includes 21 implementations: Askama, Astro, Dioxus, Exact, Go html/template, Handlebars, Jinja2, jte, Leptos, Marko, Next.js, PHP, Proa, Rails, React, Rocker, Sailfish, Svelte, SvelteKit, Topcoat and Vue. Coverage varies by experiment; adapted fixtures and unsupported workloads are explicitly marked. See the renderer roster and framework classifications.

What the benchmarks measure

Experiment Measurement
SSR Rendering Prepared data to fresh owned HTML output; render latency and peak process RSS
Framework SSR Production framework routing through the complete HTTP response
HTTP Sustained throughput, equal-load latency, CPU and memory
Streaming Streamed shell and resolved response completion under load
Cold Start Fresh server process to its first complete response

Workloads include a component page, product grid, 1,000-row table, Airbnb landing page, Nike catalog, GitHub pull-request review, Sentry logs and ESPN game page. These are shared benchmark re-creations, not measurements of those companies’ sites.

Compare results within the same experiment: render-only time excludes HTTP, and server measurements exclude browser JavaScript execution. Competitors share a machine and workload within each suite; published results must pass output parity, sampling and source-integrity checks. Read the measurement protocols and inspect the rendering results or HTTP, streaming and startup results.

Run an SSR benchmark

Use Bun 1.4.2. This short contributor run checks selected adapters without installing every language toolchain or replacing published results.

bun install --frozen-lockfile
bun node_modules/playwright/cli.js install chromium
bun run bench list
bun run bench doctor rendering
bun run bench run rendering --renderers react,vue --workloads cards

Smoke results validate implementations; use the publication protocol for rankings. See CONTRIBUTING.md to add a framework, change a workload or run the full suite, and the GCP campaign guide for isolated parallel benchmark runs.

Repository guide

Benchmarks · Experiments · Tooling · Website · Website data · Fixtures · Reports and protocols

Keep the latest validated capture and its raw samples per experiment; older captures remain in Git history. See the retention rules for publication and cleanup. Run bun run check for repository checks, bun run --cwd site test:browser for browser checks, and bun run check:publication for the strict publication gate.

Related work: eknkc’s SSR Framework Benchmark, an earlier comparison focused on JavaScript SSR stacks.

Maintained by Proa Labs, which develops Proa, one of the measured frameworks. Performance is one input to choosing a framework; features and integration choices matter too.

Apache-2.0 · Third-party attribution

About

SSR benchmarks for web frameworks and template engines. Compare server-side rendering, HTTP throughput, streaming, cold starts and memory usage with reproducible workloads.

Topics

Resources

Contributing

Stars

7 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages