The WebAssembly API delegation is the clever part, guest wasm escapes the interpreter tax by running on the host Wasmer runtime directly. The question it raises: when my Node app instantiates arbitrary wasm bytes and they execute outside QuickJS.wasm, do those child instances inherit the parent sandboxes memory and CPU accounting, or are they a separate domain? Thats historically the hole embedded JS sandboxes leak through once they grow an FFI. Also curious how much of the 100ms vs 10ms SSR gap you expect V8 to close, versus whats owed to the wasm boundary itself.
•
u/geekonthegrill 15h ago
The WebAssembly API delegation is the clever part, guest wasm escapes the interpreter tax by running on the host Wasmer runtime directly. The question it raises: when my Node app instantiates arbitrary wasm bytes and they execute outside QuickJS.wasm, do those child instances inherit the parent sandboxes memory and CPU accounting, or are they a separate domain? Thats historically the hole embedded JS sandboxes leak through once they grow an FFI. Also curious how much of the 100ms vs 10ms SSR gap you expect V8 to close, versus whats owed to the wasm boundary itself.