Orchestration Costs
A placeholder for notes from the multi-threading and wasm performance work. The first shape of the argument is simple: raw compute time is only part of the story; setup, dispatch, copying, worker coordination, and wasm instantiation all show up on the bill.
What The CSV Is Measuring
Block this section out with the benchmark setup: loop variant, execution mode, worker count, input size, iteration count, total elapsed time, compute time, and the derived orchestration column.
Cold vs Hot Loop Cost
This chart compares average cold/setup-inclusive cost against average hot-loop cost per element iteration. The tabs separate the run by iteration count, and the colors separate JavaScript, wasm, and wasm SIMD.
Loading benchmark data...
Notes To Fill In
- Where worker startup dominates and where it disappears into larger jobs.
- How wasm single-threaded runs compare with JavaScript single-threaded runs.
- Why the fastest line is not always the most useful architectural answer.
- Which measurements should be rerun or expanded before treating this as a conclusion.