Pure Wasm Compute
A CPU loop with no JS import. Shows baseline Wasm execution and optimizer differences between the two modules.
WebAssembly Browser Benchmark
JSPI vs Asyncify
Measures performance on the exact browser and machine that opens this page. This is not a server benchmark.
loading…
Benchmark Settings
Lower values are faster. For more stable numbers: close browser DevTools, disable power-saving mode, and run the benchmark multiple times.
Environment
Comparison
| Operation | Metric | Asyncify | JSPI | Faster | Ratio |
|---|---|---|---|---|---|
| No measurements yet. | |||||
What Gets Measured
Synchronous Wasm→JS Imports
Many synchronous host calls from Wasm into JavaScript. Shows boundary overhead without Promise/Suspend behavior.
Async Promise Roundtrips
Wasm calls one asynchronous JS import per iteration. JSPI uses WebAssembly.Suspending/promising; Asyncify uses an instrumented resume-state machine.
Nested Async
An async operation with additional nested work. This exposes Suspend/Resume overhead with more call-stack context.