You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2d4d43b
Browse filesBrowse the repository at this point in the historyBrowse files
docs(perf): Store / List Delivery Lane — the Octane board campaign (2026-08-16 → 09-18) and the board workflow
Hand-off for the store/list performance campaign, so it can continue in a
fresh session. performance-experiments.md gains the lane: goal and
rulings, instruments (Octane fork, local dbmon harness, results dirs),
the seven experiments in order with PR/branch, measurement and verdict
(patch channel + driver #3079/#3091/#3229, regions branch, unified For
slot #3281 / engine #3308, small-move #3227, coarse reads #3275,
create-floor diets #3270/#3367/#3368, props/spread/view work), the fixture
authoring rules and what the two passes covered, the uibench findings
(endpoint cloning 7.7x -> 2.5x; signal shape 0.46x the reconcile shape on
96/96 cases, ruled idiomatic), the todomvc add100 4x that was measurement
noise, the Sep 9 -> Sep 17 board with its caveats, standing lessons, and
the ordered open targets (disposal first). benchmarking-strategy.md gains
the Octane board workflow: fork/branch, linking next, running, comparing,
the gotchas each learned the hard way, and the single-op profiling
method.
Co-authored-by: Claude via Cursor <[email protected]>
bundle-size uibench. ~45–60 minutes on an idle machine. `bench.mjs`
424
+
builds every fixture and boots the preview servers itself; each suite
425
+
runs its correctness gates before timing, so a fixture change that breaks
426
+
the DOM contract fails the suite rather than posting numbers. Exit code 1
427
+
means _some_ gate failed — read the tail of the log; on 2026-09-17 the
428
+
failures were Octane's own targets.
429
+
430
+
Then `node benchmarks/board-compare.mjs <dirA> <dirB> [labelA labelB]`
431
+
for the two-sided geomean board (timed ops only). For a single suite,
432
+
`node benchmarks/<suite>/run.mjs <iterations>` with
433
+
`TARGETS='[{"name":"solid","url":"http://localhost:<port>/"}]'` against a
434
+
`pnpm --filter <fixture> preview` you started yourself.
435
+
436
+
**Gotchas, each learned the hard way:**
437
+
438
+
-`PLAYWRIGHT_BROWSERS_PATH` is set in the agent environment to a sandbox
439
+
cache; unset it or Chromium "doesn't exist".
440
+
- Long runs and preview servers must be tool-managed background tasks
441
+
(block-until 0). `nohup … &` from a tool shell dies with the shell —
442
+
silently, a minute in, leaving orphaned preview servers on their ports.
443
+
- Eight samples is the default; on sub-5 ms ops the median is bimodal
444
+
under the harness's `gc()` + 40 ms idle protocol. Read `min` beside
445
+
the median. Any single-op ratio over 2× is "rerun in isolation" until
446
+
it reproduces — todomvc `add100` read 4.3× on the board and 1.2× on a
447
+
quiet machine.
448
+
-`board-compare` uses timed ops. Do not hand-roll a geomean over "all
449
+
ops": the result JSONs also carry structural gate counters
450
+
(`nodes_deep`, `comments_*`, `text_*`) that look like numbers.
451
+
- Octane's own fixtures can regress or fail their gates between upstream
452
+
releases (0.2.13 did both). When the Solid/Octane ratio moves, check
453
+
Octane's _absolute_ times against the previous run before believing it.
454
+
- The bundle-size suite's app/framework split is meaningless under local
455
+
links (framework shows ~700 B); totals are fine.
456
+
-`signal-favoring` swings between runs by design (one text node);
0 commit comments