Evidence

Yichus and React Update-Enqueue Throughput Benchmark

How fast can each engine accept state updates? Three Bosatsu fixtures compiled by Yichus, against React 18 with useState, in your browser.

Measurement procedure and interpretation

Ops/sec is update calls divided by summed batch time. It is not committed renders per second, frame rate, or end-to-end interaction latency.

Numbers vary by browser, machine, batching choice, and scheduler behavior. Run multiple times and compare only runs with the same controls.

Sources: single-state Bosatsu fixture, 10-item list Bosatsu fixture, 10-state targeted Bosatsu fixture.

Keep the batch size and flush delay fixed when comparing rows.

Result key: Y means Yichus and R means React. The writes counts include warmup and timed update calls. The speedup ratio is React average call time divided by Yichus average call time. Batches stop at 1,000 calls or the 8ms timer threshold, with at least a 25ms yield between them. Startup is the Yichus-only time from loading its compiled script through initialization and the first committed DOM; it is not part of that ratio. Results exist only in this live page and disappear on reload. Each row shows the effective batch size, flush setting, browser user-agent, and platform recorded at that scenario's start. The rows are not persistent raw benchmark artifacts.
Scenario Yichus avg (ms) Yichus ops/sec React avg (ms) React ops/sec Speedup vs React
Click a benchmark button.

Ask your agent about anything here; it has the detail.

Where this fits

What this is about: Compiled UI updates