alonso.torres b955a2fc68 ✨ Add a component sync benchmark with a recorded baseline ...

The coming refactors and fixes change sync code, and a slowdown must be
seen and explained in the commit that causes it. A JVM benchmark now
times component sync on fixed-size worlds:
- one main into 10, 100 and 1000 copies;
- a change in the deepest of three nesting levels;
- a chain of dependents (a in b in c, with copies of each);
- a variant switch in a main with 100 copies;
- a library update into a file with 500 copies.

Each world is built once; only the sync an edit causes is timed, run
to a fixpoint as the frontend watcher does. Each checks its result, so
a world that synced nothing fails instead of timing nothing.

`scripts/bench-components record` writes the baseline, recorded here on
the code before this commit; `scripts/bench-components` compares against
it and exits 1 when a world is more than 10% slower. It compares the lower
quantile: with the devenv running, the mean of the same code moved
from 0.41 to 1.13 of the baseline, the lower quantile by under 12%.

2026-10-13 19:58:07 +02:00

..

bench-components

✨ Add a component sync benchmark with a recorded baseline

2026-10-13 19:58:07 +02:00

repl

💄 Add cosmetic improvements to common scripts/repl

2025-05-07 12:14:51 +02:00

test

⬆️ Update devenv dependencies (#11790)

2026-09-22 10:22:31 +02:00

test-quiet.js

📎 Standardize test scripts and add execution discipline docs

2026-07-16 14:57:05 +00:00