4 ms·
JS <--> WASM function calls are not an issue[1], passing large amounts of data is though. 1. https://hacks.mozilla.org/2018/10/calls-between-javascript-and-web
by elenchev 5y ago
JS <--> WASM function calls are not an issue[1], passing large amounts of data is though.
1. https://hacks.mozilla.org/2018/10/calls-between-javascript-and-webassembly-are-finally-fast-%F0%9F%8E%89/ https://hacks.mozilla.org/2018/10/calls-between-javascript-a...
- sime2009 5y agoDoes anyone know if that is also the case on V8?
- flohofwoe 5y agoJS/WASM calls are fast in V8, and still seem to be improved from time to time (e.g. see: https://v8.dev/blog/v8-release-90#webassembly https://v8.dev/blog/v8-release-90#webassembly), not sure about any large data optimizations (TBH I'm not sure what this is about though, because usually one would use JS slices into the WASM heap to avoid redundant copying)
- cdcarter 5y agoThat works if the data is already in the Wasm linear memory and you need to access it from JS. If you have strings (or whatever) in JS, you need to copy them into the linear memory for the Wasm module to use.