4 ms·
Cool to see this stuff getting out into the wild, long time coming! What is the current state of these -- do simd wasm ops run in ffox/chrome/edge/safari, and
by lmeyerov 5y ago
Cool to see this stuff getting out into the wild, long time coming!
What is the current state of these -- do simd wasm ops run in ffox/chrome/edge/safari, and does the data have to be slowly bulk copied back-and-forth from a worker (heartbleed removal of zero-copy ownership transfers)?
We love js typed arrays and columnar analytics -- graphistry contributed the first years of Apache Arrow JS -- but intentionally didn't do wasm for kernels because of this kind of stuff, despite promising internal multicore etc prototypes. A surprise win for us of GPU python/js offloading to the server has been not just scale but perf reliability. Curious how much it has improved in the typical case, as it always made sense on paper!
- brrrrrm 5y agoYep, you still need to bulk copy memory around if it already exists. If you own the memory, though, you can avoid copying (wasm has "import") but you'll need to manage that manually. I've found the cleanest approach for me is to have modules allocate space for inputs and outputs and then try to get functions to write directly into the input space. Either way, nothing available is super friendly for user provided arrays or canvas interactions.