METRICUM LAB / LOCAL EXERCISE

One workload. Three scheduling strategies.

Record a real click in Chrome DevTools → Performance → Interactions. Compare blocking, cooperative yielding, and the timer fallback. This page does not calculate INP or send telemetry.

The workload is synthetic CPU work. Elapsed completion time is not interaction latency. A shorter interaction must not silently discard work.

Choose the workload

Work items (1,000–3,000,000)

Pings acknowledged: 0

Ready. Record first, then press a run button.

Result

Work completed

No completed result for this run.

What to verify

All completed runs with the same workload must produce the same checksum. Try Ping during work, cancellation, and a second run. The blocking version cannot process Cancel until its synchronous task ends. Yielding makes opportunities for other work; it does not guarantee a paint at every yield.

Keep browser, machine, workload and CPU-throttling setting constant. Save traces separately. Do not use these numbers as predicted improvements for another site.