WORKER / WASM DEMO
Treat a remote sheet as addressable areas that may load, fail, expire, and reload independently.
The UI describes visible areas through backend ports. A production remote backend can expose loading and failure state while preserving the same grid contract used by the worker-backed demos.
/**
* Seed for the "performance" demo — a 100,000-row × 8-column generated
* dataset (800,000 data cells) loaded through the worker's chunked
* import-session API (`beginImport` / `importChunk` / `commitImport`),
* never through per-cell `setCell` calls (see `seed-formulas.ts` for that
* pattern, which is fine at ~20 cells but would be ~400,016 RPC round
* trips here).
*
* Mode choice — `direct`, not `atomic`: the WASM worker runtime caps
* `atomic` import sessions at `MAX_IMPORT_SESSION_NORMALIZED_CELLS`
* (200,000 cells; see `worker-runtime.ts`) because an atomic commit
* installs the whole staged batch as one full-sheet replace. `direct`
* mode has no such session-wide cap — each chunk lands additively in the
* live workbook via the engine's native `bulk_import_cells` batch call —
* so it is the only session mode that can reach the ~400k-cell target.
* The WASM/TS perf bench (`excel/solid-excel/test/perf-ts-vs-wasm-
* report.md`) measured `bulk_import_cells` on pure-literal batches at
* 887ms for 500,000 cells in one call; chunked at ~8,000 cells/call the
* total native cost for this seed's ~400k literal cells should land
* comfortably under a couple of seconds.
*
* Per-row formulas were deliberately NOT used for `revenue`: `direct`
* mode parses formula text eagerly per chunk (unlike `atomic`, which
* parks formula text unparsed until commit), and the same perf report