Measuring

Measure the work caused by an interaction and the time it takes on your target devices.

• Binding runs: increment a counter inside the expression, as above.
• DOM mutations: a MutationObserver with takeRecords() after flushSync().
• Node creation: spy on Node.prototype.cloneNode and Document.prototype.createElement.
• Row creation and disposal: counters in the row component and its onCleanup.

For wall-clock numbers use your browser's profiler on a production build, or the repository's row benchmark (below). For a view of signals, effects and updates in a running app use @shadow-js/devtools. Besides the row benchmark, the repository has benchmarks/micro/run.mjs (npm run bench -w @shadow-js/bench-micro, after npm run build -w @shadow-js/core). It compares @shadow-js/core with Solid 1.9 on identical graph workloads and prints the median of seven runs for:

docs/STATUS.md records the result as on par with or faster than Solid 1.9 on these workloads; the figures depend on your machine, so run the script instead of quoting a number. It measures the reactive core only, not DOM rendering.