Overview
Benchmarks
Benchmarks are part of Mreact's development loop. They are used to watch primitive runtime behavior, browser DOM costs, app-router throughput, client bundle size, route artifact shape, and deployment startup paths.
What we measure
- Primitive DOM work - Keyed list operations, row selection, event target creation, and memory-sensitive DOM cases are separated from lower-level reactivity microbenchmarks. For cross-framework keyed DOM comparisons, the official krausest/js-framework-benchmark harness is the reference, because it maintains the peer-framework adapters and keyed validation rules.
- Primitive reactivity microbenchmarks - Source writes, text bindings, computed fan-out, and computed fan-in stay in the repository as local regression signals. They are useful for Mreact runtime development, but they are not a replacement for official DOM benchmark results from the krausest harness.
- Primitive framework adapters - Marko, Vue, Svelte, Angular, Qwik, React, Solid, and Mreact run local primitive cases for context. Numbers from peer-framework adapters in the local runner are indicative only; the official harness is the reference for cross-framework comparisons.
- Browser runtime behavior - How the same DOM-heavy primitive cases behave in real Chromium rather than only in the server-side benchmark harness.
- App router and deployment paths - How server rendering, streaming, static cache hits, middleware, route matching, cold starts, build time, and adapter targets behave under app-router workloads.
- Router framework adapters - Marko Run, Nuxt, SvelteKit, Analog, Qwik City, SolidStart, TanStack Start, Next.js App Router, and Mreact app router run production router fixtures where practical.
- Client bundle shape - How much JavaScript is shipped for server-only routes and interactive routes after gzip compression.
- Route artifact boundaries - Whether middleware, redirects, loaders, server actions, layouts, and render modules stay separated enough to avoid unnecessary imports.
- Package-level microbenchmarks - Store, virtual list, query, forms, and auth microbenchmarks catch non-router regressions even when they are not rendered as public ranking cards.
How to read results
Treat benchmark numbers as trend signals, not universal promises. Compare runs with the same Node version, adapter target, route set, and build mode before drawing conclusions.
Resumability-oriented frameworks such as Qwik and Marko are designed around delaying or avoiding client-side activation, not only around already-active update paths. Primitive DOM-update cases mostly measure already-active update paths, and the browser interaction cases use small synthetic routes, so read interaction timing together with shipped JavaScript size, startup work, and whether unused UI needs to activate at all.
For keyed table operations such as create rows, replace rows, partial update, select row, append rows, remove row, swap/reorder rows, and clear rows, the source of truth is the official krausest/js-framework-benchmark harness. The local primitive runner remains useful for quick regression checks and experiments, but it is not an authoritative cross-framework comparison.
The keyed table results include two React-compatibility Mreact fixtures. mreact-react-compat is the compiler-lowered path: the source stays React-compatible JSX, and the Mreact compiler lowers proven-safe state text, prop, and event bindings into reactive DOM operations. mreact-react-compat-vdom is the virtual-DOM compatibility path: the same app shape runs through the React-compatible runtime without those DOM-binding lowerings. Compare the two to separate compatibility runtime cost from the compiler's normal DOM-binding optimizations.
Measuring route delivery
A route's imports in .mreact/client/manifest.json lists its direct static imports. A shared chunk can import more chunks, so summing only route.script, route.navigationScript, and route.imports can undercount the JavaScript a browser needs. Follow manifest.chunks[].imports transitively and count each file once. Include navigation's dependencies when budgeting navigation startup, including on a server-rendered route without a client entry. Keep unfetched dynamic imports separate; measure their static dependencies when an interaction actually loads them.
This Node script measures a JavaScript budget for the home route including navigation startup. Run it from the application directory after a production build. It uses Brotli quality 11 for each asset, so the result is a compression estimate rather than observed CDN transfer bytes.
import { readFile } from "node:fs/promises";
import { join } from "node:path";
import { brotliCompressSync, constants } from "node:zlib";
const clientDir = ".mreact/client";
const manifest = JSON.parse(await readFile(join(clientDir, "manifest.json"), "utf8"));
if (!Array.isArray(manifest.chunks)) {
throw new Error("This manifest lacks a chunk graph; inspect emitted static imports or browser requests instead.");
}
const route = manifest.routes.find((entry) => entry.path === "/");
if (!route) throw new Error("Home route is missing.");
const chunks = new Map(manifest.chunks.map((chunk) => [chunk.file, chunk]));
const files = new Set();
function visit(file) {
if (!file || files.has(file)) return;
files.add(file);
for (const dependency of chunks.get(file)?.imports ?? []) visit(dependency);
}
visit(route.script);
for (const file of route.imports ?? []) visit(file);
if (route.navigation) visit(route.navigationScript);
let rawBytes = 0;
let brotliBytes = 0;
for (const file of files) {
if (!file.endsWith(".js")) continue;
const content = await readFile(join(clientDir, file));
rawBytes += content.byteLength;
brotliBytes += brotliCompressSync(content, {
params: { [constants.BROTLI_PARAM_QUALITY]: 11 },
}).byteLength;
}
console.log({ rawBytes, brotliBytes });Keep the application source, lockfile, route set, build target, source-map mode, public environment values, and compression settings fixed when comparing framework versions. Preserve each build's assets and manifest separately. For older manifests without chunks, reconstruct the graph from emitted static imports or record browser requests; treating a missing graph as an empty graph gives an incomplete total. A production Sentry or analytics configuration can change the result, so run a release budget with the actual production configuration as well.
Chunk names describe bundler naming choices, not exclusive ownership. A chunk named after a small component can also contain shared runtime code. In particular, mreact-router-compat in a generated virtual-module name is the router's bundler adapter namespace; it does not establish that React compatibility is loaded. Native boundary helpers can contain compatibility checks without importing the React-compatible mounting runtime. Check the reachable implementation and imports before attributing a size increase to compatibility.
Sharing hydration helpers reduces duplication across route entries, but it can change chunk placement and per-file compression. A smaller multi-route session does not guarantee a smaller cold load for every route. Upgrades spanning several releases also include rendering and reactivity fixes, so compare adjacent versions when attributing a regression to a particular optimization. Keep route budgets as explicit application checks instead of relying on a release-wide size claim.
Latest results
Categories
js-framework-benchmark keyed DOM benchmarks
js-framework-benchmark.md / 13 ranking cards / View source on GitHub / Official js-framework-benchmark harness
create rows
9 entries
replace all rows
9 entries
partial update
9 entries
select row
9 entries
swap rows
9 entries
remove row
9 entries
create many rows
9 entries
append rows to large table
9 entries
clear rows
9 entries
ready memory
9 entries
run memory
9 entries
repeated clear memory
9 entries
total byte weight
9 entries
Router benchmarks
router.md / 52 ranking cards / View source on GitHub
app client bundle gzip bytes (server-only page)gzip bytes
11 entries
Measures gzip-compressed client JavaScript shipped for a route with no user-authored interactivity.
app client bundle gzip bytes (interactive page)gzip bytes
11 entries
Compatibility alias for gzip-compressed client JavaScript fetched by the minimal button-and-state interactive route after idle settle. mreact variant spread: +201.47%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app client bundle gzip bytes (interactive page, minimal opt-out)gzip bytes
11 entries
Measures the same interactive route while opting out of optional client navigation runtime where the framework supports it. mreact variant spread: +588.97%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app render 1000 nodesops/sec
11 entries
Renders a production app route that emits 1,000 simple text spans. mreact variant spread: +1.99%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app streaming 1000 nodesops/sec
11 entries
Streams a production app route with 1,000 simple text spans and validates the complete response body. mreact variant spread: +5.1%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app streaming first byte 1000 nodesms
11 entries
Measures elapsed time until fetch resolves response headers for the real streaming route. mreact variant spread: +20.79%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app streaming first chunk 1000 nodesms
11 entries
Measures elapsed time until the first response body chunk arrives for the real streaming route. mreact variant spread: +24.2%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app streaming full body 1000 nodesms
11 entries
Measures elapsed time until the complete real streaming response body is consumed and validated. mreact variant spread: +0.32%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app real streaming 1000 nodes (async 50ms)ms
11 entries
Measures complete response latency for a route whose body waits on a 50 ms async boundary. mreact variant spread: +2.02%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app parallel async boundaries 2x50msms
11 entries
Measures complete response latency for two sibling 50 ms async boundaries; parallel renderers stay near one boundary. mreact variant spread: +0.13%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app static cached route 1000 nodesops/sec
6 entries
Renders a static-cacheable app route with 1,000 simple text spans after the production server has warmed it. mreact variant spread: +2.75%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app dynamic-attr grid 200 cellsops/sec
11 entries
Renders 200 cells with many dynamic escaped attributes, inline style values, and text content. mreact variant spread: +1.86%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app dynamic route params dataops/sec
11 entries
Renders a dynamic route that combines route parameters with server data before producing HTML. mreact variant spread: +2.84%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app HTTP v2 burst throughput (max 100 in-flight)ops/sec
11 entries
Isolated HTTP/1.1 burst load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 burst p50 latency (max 100 in-flight)ms
11 entries
Isolated HTTP/1.1 burst load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 burst p95 latency (max 100 in-flight)ms
11 entries
Isolated HTTP/1.1 burst load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 burst p99 latency (max 100 in-flight)ms
11 entries
Isolated HTTP/1.1 burst load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 burst server RSS delta (max 100 in-flight)bytes
9 entries
Isolated HTTP/1.1 burst load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 steady throughput (max 100 in-flight)ops/sec
11 entries
Isolated HTTP/1.1 steady load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 steady p50 latency (max 100 in-flight)ms
11 entries
Isolated HTTP/1.1 steady load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 steady p95 latency (max 100 in-flight)ms
11 entries
Isolated HTTP/1.1 steady load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 steady p99 latency (max 100 in-flight)ms
11 entries
Isolated HTTP/1.1 steady load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app HTTP v2 steady server RSS delta (max 100 in-flight)bytes
10 entries
Isolated HTTP/1.1 steady load. All five metrics derive from the same trials; workload and connection metadata are retained in JSON. Methodology v2 uses separate orchestrator, load generator and production server processes. All five metrics share the same trials. RSS is a single server PID's before/after delta, not a peak or process-tree total; negative samples remain in JSON but are excluded from RSS rankings. Route/cache conditions still differ across adapters (mreact uses /static-page with its route cache); consult httpTrials before comparing frameworks. These measurements are not directly comparable to legacy concurrent probes. Steady windows share one warmed connection pool; burst trials start fresh pools, not cold servers.
app browser v2 domcontentloaded initial content observedms
10 entries
Verified initial content observed in a fresh domcontentloaded trial. SSR content is checked separately with JavaScript disabled. E2E includes Playwright; event-to-DOM includes observer delivery, not paint or INP. Browser methodology v2 verifies SSR separately with JavaScript disabled and requires two working counter interactions. Related metrics share trials and IDs in browserTrials. E2E includes Playwright automation; event-to-DOM ends at MutationObserver delivery, not paint or INP. Network-idle profiles include the explicit quiet-period wait before interaction. These measurements are not directly comparable to legacy browser probes. mreact variant spread: +18.67%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app browser v2 domcontentloaded navigation to first verified updatems
10 entries
Verified navigation to first verified update in a fresh domcontentloaded trial. SSR content is checked separately with JavaScript disabled. E2E includes Playwright; event-to-DOM includes observer delivery, not paint or INP. Browser methodology v2 verifies SSR separately with JavaScript disabled and requires two working counter interactions. Related metrics share trials and IDs in browserTrials. E2E includes Playwright automation; event-to-DOM ends at MutationObserver delivery, not paint or INP. Network-idle profiles include the explicit quiet-period wait before interaction. These measurements are not directly comparable to legacy browser probes. mreact variant spread: +12.38%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app browser v2 domcontentloaded first click E2Ems
10 entries
Verified first click E2E in a fresh domcontentloaded trial. SSR content is checked separately with JavaScript disabled. E2E includes Playwright; event-to-DOM includes observer delivery, not paint or INP. Browser methodology v2 verifies SSR separately with JavaScript disabled and requires two working counter interactions. Related metrics share trials and IDs in browserTrials. E2E includes Playwright automation; event-to-DOM ends at MutationObserver delivery, not paint or INP. Network-idle profiles include the explicit quiet-period wait before interaction. These measurements are not directly comparable to legacy browser probes. mreact variant spread: +7.71%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app browser v2 domcontentloaded first click event-to-DOMms
10 entries
Verified first click event-to-DOM in a fresh domcontentloaded trial. SSR content is checked separately with JavaScript disabled. E2E includes Playwright; event-to-DOM includes observer delivery, not paint or INP. Browser methodology v2 verifies SSR separately with JavaScript disabled and requires two working counter interactions. Related metrics share trials and IDs in browserTrials. E2E includes Playwright automation; event-to-DOM ends at MutationObserver delivery, not paint or INP. Network-idle profiles include the explicit quiet-period wait before interaction. These measurements are not directly comparable to legacy browser probes. mreact variant spread: +242.86%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app browser v2 networkidle first click E2Ems
10 entries
Verified first click E2E in a fresh networkidle trial. SSR content is checked separately with JavaScript disabled. E2E includes Playwright; event-to-DOM includes observer delivery, not paint or INP. Browser methodology v2 verifies SSR separately with JavaScript disabled and requires two working counter interactions. Related metrics share trials and IDs in browserTrials. E2E includes Playwright automation; event-to-DOM ends at MutationObserver delivery, not paint or INP. Network-idle profiles include the explicit quiet-period wait before interaction. These measurements are not directly comparable to legacy browser probes. mreact variant spread: +7.46%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app browser v2 networkidle first click event-to-DOMms
10 entries
Verified first click event-to-DOM in a fresh networkidle trial. SSR content is checked separately with JavaScript disabled. E2E includes Playwright; event-to-DOM includes observer delivery, not paint or INP. Browser methodology v2 verifies SSR separately with JavaScript disabled and requires two working counter interactions. Related metrics share trials and IDs in browserTrials. E2E includes Playwright automation; event-to-DOM ends at MutationObserver delivery, not paint or INP. Network-idle profiles include the explicit quiet-period wait before interaction. These measurements are not directly comparable to legacy browser probes. mreact variant spread: +200%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app browser v2 networkidle second click E2Ems
10 entries
Verified second click E2E in a fresh networkidle trial. SSR content is checked separately with JavaScript disabled. E2E includes Playwright; event-to-DOM includes observer delivery, not paint or INP. Browser methodology v2 verifies SSR separately with JavaScript disabled and requires two working counter interactions. Related metrics share trials and IDs in browserTrials. E2E includes Playwright automation; event-to-DOM ends at MutationObserver delivery, not paint or INP. Network-idle profiles include the explicit quiet-period wait before interaction. These measurements are not directly comparable to legacy browser probes. mreact variant spread: +62.6%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app browser v2 networkidle second click event-to-DOMms
10 entries
Verified second click event-to-DOM in a fresh networkidle trial. SSR content is checked separately with JavaScript disabled. E2E includes Playwright; event-to-DOM includes observer delivery, not paint or INP. Browser methodology v2 verifies SSR separately with JavaScript disabled and requires two working counter interactions. Related metrics share trials and IDs in browserTrials. E2E includes Playwright automation; event-to-DOM ends at MutationObserver delivery, not paint or INP. Network-idle profiles include the explicit quiet-period wait before interaction. These measurements are not directly comparable to legacy browser probes. mreact variant spread: +400%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app loader client navigation route-to-routems
7 entries
Measures browser client navigation to a route with loader data, covering data-bearing SPA transitions. mreact variant spread: +8.01%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app client navigation back-forward restorems
9 entries
Measures browser back-forward restoration after SPA navigation so history snapshot regressions are visible. Includes Playwright navigation commands and locator waits around both traversals. The result includes automation scheduling and is not a direct measure of browser DOM work. mreact variant spread: +134.39%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app client navigation back-forward first visible DOMms
9 entries
Measures popstate-to-first-visible-route-DOM for back and forward inside the browser; excludes Playwright command and locator waits, later state updates, and paint. The sum of back and forward popstate-to-first-visible-route-DOM intervals measured by MutationObserver inside the browser. The same first-visible count 0 or 1 rule applies to every adapter; later state updates are excluded. It includes asynchronous route fetching after popstate but excludes Playwright command and locator waits; it is not paint or INP and is not directly comparable to the Playwright wall-time case. mreact variant spread: +7.23%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app client navigation route-to-routems
9 entries
Measures route-to-route client navigation latency in a real browser when the adapter provides a browser probe. mreact variant spread: +2.04%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app SSR HTML gzip bytes 1000 nodesgzip bytes
11 entries
Measures gzip-compressed HTML payload bytes for the 1,000-node SSR route, complementing client bundle size cases. mreact variant spread: 0%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app client bundle gzip bytes before interaction (interactive page)gzip bytes
11 entries
Measures gzip-compressed client JavaScript completed before the minimal interactive route responds to its first click. mreact variant spread: +201.47%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app client bundle gzip bytes after idle settle (interactive page)gzip bytes
11 entries
Measures gzip-compressed client JavaScript fetched by the minimal interactive route after the browser reaches networkidle. mreact variant spread: +201.47%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app client bundle gzip bytes (interactive page, 3 shared routes)gzip bytes
3 entries
Measures a three-route interactive app that shares client route runtime chunks, making per-route glue dedup visible. mreact variant spread: +191.95%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app build output gzip bytesgzip bytes
11 entries
Measures gzip-compressed production build output size when the adapter exposes build artifacts. mreact variant spread: +0.04%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app 100 islands verified interaction E2Ems
3 entries
Loads 100 islands and verifies every independent 0-to-1 update with ordinary Playwright clicks. Includes navigation and all 100 operations; not hydration time. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. Includes navigation and sequential Playwright interactions with every island, checking independent state after each click. This is functional end-to-end duration, not hydration time. mreact variant spread: +1.54%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app dev cold startms
3 entries
Starts the framework dev server for a minimal app and reports server readiness latency. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +15.97%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app dev first request latencyms
3 entries
Requests a minimal app route from a warm dev server and reports first request latency. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +387.21%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app dev HMR update latencyms
3 entries
Edits a route module while the dev server is running and reports time until the changed response is observable. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +408.42%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app 1000 route match latencyms
3 entries
Builds a 1,000-route app and reports request latency for a route near the end of the route table. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +132.92%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app 1000 route cold startms
3 entries
Builds a 1,000-route app and reports production server cold-start latency for that route scale. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +3.21%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app 1000 route build timems
3 entries
Reports production build time for a 1,000-route app to catch route-count scaling regressions. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +35.73%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app 1000 route RSS deltabytes
3 entries
Reports process RSS growth while building and serving a 1,000-route app. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +6.95%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app server action form POST roundtripms
3 entries
Renders a form with an inferred server action, submits the encoded form POST, and reports action roundtrip latency. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +3.82%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app nested layouts depth 5ms
3 entries
Renders a route under five nested layouts, guarding against sequential layout shell regressions. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +32.42%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app Cloudflare Worker request latencyms
3 entries
Builds the Cloudflare Pages worker bundle and reports request latency through its exported fetch handler. A workerd/Miniflare harness should replace this fallback once the local workerd path-resolution failure is fixed. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +29.74%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
app server cold startms
3 entries
Measures production server cold-start latency when the adapter can isolate startup from build work. This section currently compares mreact app-router variants only; it is not a cross-framework ranking. mreact variant spread: +2.37%. This includes implementation and configuration differences; it is not measurement noise or a statistical significance threshold.
Primitive DOM benchmarks
primitive.md / 3 ranking cards / View source on GitHub
keyed reverse 1k rowsms
10 entries
Reverses 1,000 keyed rows and verifies that DOM node identity is preserved.
create 1k event targetsms
10 entries
Creates 1,000 button event targets and measures initial interactive wiring cost without dispatching events.
repeated create update clear memorybytes
10 entries
Reports heap growth after repeatedly creating, updating, and clearing 1,000-row lists.
Primitive reactivity microbenchmarks
primitive.md / 4 ranking cards / View source on GitHub
source write with subscriber 1kms
3 entries
Updates 1,000 fine-grained source values when each source has one live non-DOM subscriber, separating direct source write overhead from aggregate computed fan-in and framework-level array update work.
text binding update 1kms
10 entries
Updates one reactive text value that is bound to 1,000 text nodes.
computed fan-out 1kms
10 entries
Updates one source value that fans out through a derived value into 1,000 displayed text nodes.
source write 1kms
3 entries
Updates 1,000 fine-grained source values without subscribers, derived values, DOM writes, or framework-level re-render work, then validates the final source values. Frameworks without an equivalent source primitive report this case as unsupported.
Primitive browser benchmarks
primitive-browser.md / 4 ranking cards / View source on GitHub
browser create 1k rowsms
8 entries
Creates 1,000 keyed DOM rows in real Chromium, mirroring the primitive create case without happy-dom.
browser update every 10th in 10k rowsms
8 entries
Updates every tenth row in a 10,000-row keyed DOM in real Chromium, exposing real DOM update costs hidden by happy-dom.
browser select row in 10k rowsms
8 entries
Toggles selection attributes for one row in a 10,000-row keyed DOM in real Chromium.
browser clear 10k rowsms
8 entries
Clears a 10,000-row keyed DOM in real Chromium to validate happy-dom clear rankings against browser behavior.