3 ms·

I was playing around with server-side wasm by way of OpenCL compiled to that and interfaced via Deno. It felt pretty cool until I realized wasm is 32-bit and th

I was playing around with server-side wasm by way of OpenCL compiled to that and interfaced via Deno. It felt pretty cool until I realized wasm is 32-bit and this limits memory to 4GB for whatever process you've compiled in it. Unfortunately this obliterated it as an option for our use case. The idea is still really interesting, though. It's almost like micro-containerization. I was reading this and it's what sold me on attempting it: https://www.techtarget.com/searchitoperations/news/252527414/Server-side-WebAssembly-prepares-for-takeoff-in-2023 https://www.techtarget.com/searchitoperations/news/252527414...

lukevp 4y ago
wasm doesn’t have threads right now, so I wonder if you couldn’t just make multiple wasm processes and implement message passing between them to get around this limitation? I imagine if you’re building something where 4 gigs of Ram is a limitation, it would also benefit from using multiple CPU cores and you’d have to do multi-process for that anyway.
cube2222 4y ago
This actually seems to be experimentally supported by some runtimes, like wasmtime[0]. [0]: https://github.com/bytecodealliance/wasmtime/pull/3153 https://github.com/bytecodealliance/wasmtime/pull/3153
miloignis 4y ago
The Memory64 proposal is coming along, with experimental support in Firefox, Chrome, Wasmtime, Node.js, and Deno. ([0] has the status of the current proposals with a supported matrix) Hopefully it'll get fully supported soon! [0] https://webassembly.org/roadmap/ https://webassembly.org/roadmap/