Performance Lab
Effuse performance claims must be backed by reproducible production-build measurements. The repository performance lab owns benchmark scenarios, machine-readable reports, and conservative regression budgets.
pnpm bench:routes
pnpm bench:routes:bunBoth commands build the production core package, verify its browser entry, warm each route operation, collect 30 timing batches, and enforce median and p95 guardrails.
The route suite currently measures pattern parsing, compilation, matching,
resolution, specificity comparison, and a realistic route-table scan. Pass
--json directly to scripts/performance/route-pattern.mjs for schema-versioned
output containing units, sample configuration, runtime version, platform, and
architecture.
- Median represents the typical sampled batch.
- p95 exposes slower batches that a median can hide.
- Standard deviation and range indicate measurement stability.
- Versioned budgets catch large Effuse regressions across variable CI hardware.
- Budgets are not proof that Effuse is faster than another framework.
Cross-framework comparisons must use equivalent features, payloads, production builds, runtimes, warmup, sample counts, and hardware constraints. Results must publish losses and unmeasured areas alongside wins.
#249 tracks cold start, server-handler throughput, SSR latency, hydration and mount cost, update latency, memory, client bytes, CI baselines, and reviewed competitor fixtures.
The first route benchmark slice is current. Broader framework superiority is a goal to prove, not a status claim.