0
Fork 0
mirror of https://github.com/TanStack/router.git synced 2026-11-16 19:38:07 +00:00
router/benchmarks/memory
History 2026-09-05 23:19:05 +02:00
..
client test: apply Node compiler and GC corrections to memory workers 2026-09-05 22:42:34 +02:00
server test: run allocator controls through a dedicated Nx target 2026-09-05 23:19:05 +02:00
flame-control.ts benchmark: memory (codspeed) (#7623) 2026-06-14 12:51:10 +02:00
README.md bench(memory): stabilize CodSpeed memory benchmarks (#7730) 2026-07-02 21:44:55 +02:00
run-flame.mjs benchmark: memory (codspeed) (#7623) 2026-06-14 12:51:10 +02:00
runtime.ts test: control the memory worker old-generation GC budget 2026-09-05 22:56:30 +02:00
tsconfig.json test: apply Node compiler and GC corrections to memory workers 2026-09-05 22:42:34 +02:00

Memory Benchmarks

Dedicated memory benchmarks for TanStack Router / Start, measured with the CodSpeed memory instrument (mode: memory in .github/workflows/client-nav-benchmarks.yml). The workflow runs on every push to main except docs/examples/e2e-only pushes: CodSpeed compares a PR against the run on its merge-base commit, and a main commit without a run makes CodSpeed silently fall back to an older base — a single outlier base run then flags phantom regressions on every PR until the next run lands. (Falling back across a docs-only commit is safe: the previous run's benchmark-relevant code is identical.) Two separate benchmarks:

  • server/ (@benchmarks/memory-server) — React/Solid/Vue Start apps, requests against the built server handler (handler.fetch), Node environment.
  • client/ (@benchmarks/memory-client) — router-only React/Solid/Vue apps in jsdom.

These deliberately do not reuse the CPU scenarios in benchmarks/ssr and benchmarks/client-nav: memory benches need their own iteration counts, payload sizes, and route shapes, and tuning those must never shift the CPU baselines. Each scenario keeps a framework level (react/, solid/, vue/) so framework ports can be added without renames.

Layout

benchmarks/memory/<server|client>/
  package.json                  Nx targets: build:<framework>, test:perf:<framework>, test:flame:<framework>, test:types
  bench-utils.ts                memoryBenchOptions, seeded LCG (+ sequential request loop on the server side)
  vitest.<framework>.config.ts  aggregates scenarios/*/<framework>/vite.config.ts
  scenarios/<scenario>/<framework>/
                                one isolated app per scenario + setup.ts + memory.bench.ts + memory.flame.ts

One app per scenario; apps and bench names are stable once landed (CodSpeed continuity). Never grow an existing scenario for a new case — add a scenario. setup.ts imports the built app and exports the concrete workload; memory.bench.ts registers bench(...) directly, and memory.flame.ts runs the same workload through the Flame profiler.

How the memory instrument executes a bench

  • The bench function is warmed up, then measured exactly once, starting after a forced GC. Under plain vitest bench the suites only smoke-test: timing output is meaningless; real numbers come from CodSpeed.
  • Under CodSpeed the bench fn runs several warmup invocations plus the measured one on the same mount, so bench fns must be idempotent and module-level counters/LCGs are used where ids must never repeat across invocations.
  • Plain vitest bench never runs suite hooks (beforeAll/afterAll) and only honors tinybench's setup/teardown options; the CodSpeed runner does the exact opposite. Client benches therefore register both — in any given mode exactly one pair runs.
  • The process runs with V8 determinism flags (predictable GC schedule, --no-opt). Never call global.gc() manually in churn scenarios — their signal is accumulation across iterations, which a forced collection masks. Peak scenarios do the opposite: they set pinGcBetweenIterations on the request loop so a collection runs between iterations. Their signal is the footprint of a single request, and without pinned GC points the measured peak flips by a whole payload depending on whether iteration i's garbage is collected before iteration i+1 allocates. Because of --no-opt, allocation counts overstate production; numbers are for regression tracking, not absolute claims.
  • Keep each bench under ~1.5M allocations (instrument overhead grows past 2M); this is the main constraint when tuning iteration counts.

Bench shapes and signals

  • Churn (leak detector): N sequential iterations at steady state. If one iteration leaks L bytes, peak grows by ~N·L; healthy builds show a flat timeline floor independent of N. Tuning check: doubling N must leave peak roughly unchanged.
  • Peak (footprint): one (or very few) large operations; peak memory scaling with the workload is the signal.

Scenarios

Server

Scenario Shape Guards against
request-churn churn cross-request retention in document SSR (unique URLs)
server-fn-churn churn retention in the server-function RPC path
error-paths churn redirect/notFound/error/unmatched paths pinning contexts
aborted-requests churn dangling streams/listeners after mid-stream client aborts
peak-large-page peak per-request peak scaling with page size
streaming-peak peak streaming buffering O(document) instead of O(chunk)
serialization-payload peak double-buffering / string-copy blowups in dehydration

Client

Scenario Shape Guards against
navigation-churn churn per-navigation retention at steady state
unique-location-churn churn unbounded href/search-keyed caches (never-repeated URLs)
preload-churn churn preload-cache eviction not releasing memory
loader-data-retention churn departed routes' loader data staying pinned (gcTime 0)
mount-unmount churn router instances not collectable after dispose
interrupted-navigations churn superseded navigations retaining closures/contexts

Conventions

  • Strictly sequential work: at most one request/navigation in flight; each server response is fully consumed before the next request. Pairing a single navigation with its render signal via Promise.all([navigate, rendered]) is fine — never overlap distinct work items.
  • Randomness only via the seeded LCG in bench-utils.ts; no Math.random, Date.now, or timers with a nonzero delay — anywhere async ordering must be staged (streaming-peak's deferred sections, aborted-requests' deferred loader data and post-abort drain), chain 0ms setTimeout hops and count event-loop turns instead. A wall-clock delay races renderer work differently depending on runner load and instrumentation overhead, which makes the single measured run non-reproducible; 0ms hops fire in registration order in the timers phase, so the interleaving is a pure function of the schedule.
  • Sanity assertions run once at module load and throw on wrong status/markers, so a bench can never silently measure the wrong thing.
  • Server requests follow benchmarks/ssr conventions: document GETs send accept: text/html, server-fn requests send sec-fetch-site: same-origin with bodies precomputed at module level.
  • Client apps export mountTestApp from app.tsx; benches import the built dist/app.js; navigations use replace: true; unmount does full teardown (framework root, __TSR_ROUTER__, history.destroy()); large loader payloads are never rendered into the DOM.
  • NODE_ENV=production everywhere (the Nx targets set it).

Run

Smoke-test the CodSpeed/Vitest benchmark entrypoints and typecheck the scenarios:

pnpm nx run @benchmarks/memory-server:test:perf:react --outputStyle=stream --skipRemoteCache
pnpm nx run @benchmarks/memory-server:test:perf:solid --outputStyle=stream --skipRemoteCache
pnpm nx run @benchmarks/memory-server:test:perf:vue --outputStyle=stream --skipRemoteCache
pnpm nx run @benchmarks/memory-client:test:perf:react --outputStyle=stream --skipRemoteCache
pnpm nx run @benchmarks/memory-client:test:perf:solid --outputStyle=stream --skipRemoteCache
pnpm nx run @benchmarks/memory-client:test:perf:vue --outputStyle=stream --skipRemoteCache
pnpm nx run @benchmarks/memory-server:test:types --outputStyle=stream --skipRemoteCache
pnpm nx run @benchmarks/memory-client:test:types --outputStyle=stream --skipRemoteCache

Local attribution profiling, without CodSpeed CLI/login/sudo/upload, uses @datadog/pprof heap sampling and @platformatic/flame only to render the captured pprof files as HTML/Markdown. These targets rebuild the scenarios with --sourcemap true so the generated profile reports can point back to source; the normal CodSpeed benchmark builds are unchanged. Local aggregate scripts run with --parallel=1, and scenario test:flame targets opt out of Nx parallelism so profiling workloads do not overlap and bias each other. The Vitest aggregate configs also set fileParallelism: false so benchmark files run sequentially inside test:perf:react.

pnpm benchmark:memory:server:flame
pnpm benchmark:memory:client:flame
pnpm benchmark:memory:server:flame:solid
pnpm benchmark:memory:client:flame:solid
pnpm benchmark:memory:server:flame:vue
pnpm benchmark:memory:client:flame:vue

To profile one scenario, run its test:flame target directly:

pnpm nx run @benchmarks/memory-server-request-churn-react:test:flame --outputStyle=stream --skipRemoteCache
pnpm nx run @benchmarks/memory-client-navigation-churn-react:test:flame --outputStyle=stream --skipRemoteCache

Flame writes reports under the scenario's ignored .profiles/<timestamp>/ directory, including heap-profile-*.html and heap-profile-*.md. The memory.flame.ts entrypoints run the same workload shape as memory.bench.ts but manually start profiling after sanity/setup work and stop it after the measured workload. Treat these profiles as diagnostic heap-sampling attribution; they are not CodSpeed memory metrics such as peak memory, allocated bytes, or allocation counts. The heap sampler is stopped before profile conversion and Flame report generation, so Flame/pprof report-generation work should not appear as part of the captured workload. Flame runs do not force GC before profiling; doing so would perturb the workload and still would not make heap sampling equivalent to CodSpeed memory metrics.

Clean local Flame profile output with:

pnpm --filter @benchmarks/memory-server clean:profiles
pnpm --filter @benchmarks/memory-client clean:profiles

Client memory benches are useful for regression tracking of router/React/jsdom integration behavior, especially retained route/cache data. They are not pure browser-memory measurements, and local Flame attribution can include jsdom, React DOM, and profiler shutdown frames.

Real memory measurement, locally (requires the CodSpeed CLI, codspeed setup once to install the memory executor, and sudo; uploads results to the CodSpeed dashboard — local runs do not affect PR baselines):

WITH_INSTRUMENTATION=1 codspeed run --mode memory -- pnpm nx run @benchmarks/memory-server:test:perf:react
WITH_INSTRUMENTATION=1 codspeed run --mode memory -- pnpm nx run @benchmarks/memory-server:test:perf:solid
WITH_INSTRUMENTATION=1 codspeed run --mode memory -- pnpm nx run @benchmarks/memory-server:test:perf:vue
WITH_INSTRUMENTATION=1 codspeed run --mode memory -- pnpm nx run @benchmarks/memory-client:test:perf:react
WITH_INSTRUMENTATION=1 codspeed run --mode memory -- pnpm nx run @benchmarks/memory-client:test:perf:solid
WITH_INSTRUMENTATION=1 codspeed run --mode memory -- pnpm nx run @benchmarks/memory-client:test:perf:vue