wizer

I can't speak for rustpython, but you can partially evaluate dynamic languages in wasm with something like wizer https://github.com/bytecodealliance/wizer. So you can let the runtime do all the parsing and compiling ahead of time. We do this with javascript (quickjs). It does have a few downsides regarding memory size but it is pretty fast.

> once by the wasm runtime to compile the rust-python wasm I'm not sure what you mean by that. The runtime doesn't compile WASM, it simply executes it. There are tools for dealing with interpreter runtime overhead this by pre-initalizing the environment like Wizer[0]. ComponentizeJS[1] uses it to pre-initialize the Spidermoney engine it packages to gain fast startup times (and you can then prune the initialization only code with wasm-opt). As techniques like ComponentizeJS are also being applied for a specific set of interpreted files, you can even prune parts of the interpreter that would never be used for that specific program. If you want to go even further you could record specific execution profiles and optimize based on those. [0]: https://github.com/bytecodealliance/wizer [1]: https://github.com/bytecodealliance/ComponentizeJS

I guess you are referring to wizer [1]? (it's the closest to snapshot restore in the WebAssembly world). In case you are referring to that, the wizer strategy is valid for any Wasm runtime (and it will be fast once the Wasm module is snapshotted by wizer). If you refer towards Wasm module loading times (once a module is already been precompiled), Wasmer is already one of the fastest ones. https://github.com/bytecodealliance/wizer

There are interesting plans to speed up [the cold start latency of] V8 by compiling it to wasm[0] AFAIU the main point is that for wasm you can condense startup to a mmap operation and that you can "freeze" a running wasm process (essentially by dumping the memory/stacks to a new wasm module. In [0] they use [1] to do this. [0] https://bytecodealliance.org/articles/making-javascript-run-... [1] https://github.com/bytecodealliance/wizer

Edge functions are typically run intermittently, with their runtime stopped to free up resources between runs. Therefore a big factor is startup and shutdown speed. Containers are pretty bad there. Deno is better, and WASM is unbeatable, especially with things like Wizer[0]. [0]https://github.com/bytecodealliance/wizer

It should probably be named "Making JavaScript to startup fast on WebAssembly", since the runtime speed is not really improved by their approach. Besides that, I think Wizer [1] is both an elegant and a simple solution to speed up startup times with Wasm. So good work on that! [1] - https://github.com/bytecodealliance/wizer