Wasm vs JavaScript benchmark Browse Catalog Experiment Evidence data v1

Reduced out-of-catalog fixture · image.flood-fill.v1

Span-Stack Image Flood Fill

Fills contiguous pixel regions on a 64 × 48 image grid using span-stack queue/stack operations, comparing JavaScript vs WebAssembly.

Fixed work: 64 × 48 image grid with barrier obstacles. Fills contiguous matching color regions and calculates exact filled pixel mask counts. Reduced fixture for image.flood-fill.v1 with no timing evidence or comparative performance claim.

Run Benchmark Loop

Each run executes in a fresh module worker.

Ready. Click Start to run benchmark suite.

What it does

Traverses connected pixel spans using an explicit stack buffer to fill bounded color regions.

Why compare Wasm vs JS

Stack allocation, pixel neighbor indexing, and array bounds checking test memory management efficiency in graphic paint engines.

Source & build provenance

The controls, fixed scope, source routes, and limitations are in this raw HTML response.

Limitations & scope

  • Fixed 64 × 48 image grid with verified SHA-256 reference output.
  • Runs in a Web Worker module with 120-second hard timeout.

Multi-Language Comparison

The same kernel written in JavaScript, C, C++, Rust, and Dart (WasmGC) — compiled to WebAssembly where applicable — compared side by side on this machine. Sources: multi-language kernel sources.

Ready. Select loop iterations, then click Start.