5 ms·

Thanks! I tried to get wasmtime working but it was too much of a pain to compile in no_std mode, so I settled for wasmi instead.

herobird 1y ago
Wasmi author here. Glad to see Wasmi being used in embedded contexts were it really shines. :) I just watched the demo video of Munal OS and am still in awe of all of its features. Really impressive work!
- 9d 1y ago
  Yeah it's one of those projects were I'm so impressed that I'm saying nothing because there's nothing to say, it's just really impressive. I'm not sure what will come of this project, but it has a lot of potential to at least inspire other projects or spark important discussions around its innovations.
- Gazoche 1y ago
  Thank you! And thanks for making Wasmi, it's a really impressive project and it's the reason why I decided to go this whole WASM sandbox route (because I could embed it easily) :)
  - herobird 1y ago
    Awww, makes me very happy to hear! :) Thank you!
phickey 1y ago
Wasmtime maintainer here - curious to hear what went wrong, I and several other users of wasmtime have production embeddings under no_std, so it should do everything you need, including building out WASI preview 2 support. You can find me on the bytecode alliance zulip if you need help.
- lasiotus 1y ago
  I'm not the OP, but I have a similar experience with Motor OS: wasmi compiles and works "out of the box", while wasmtime has a bunch of dependencies (e.g. target-lexicon) that won't compile on custom targets even if all features are turned off in wasmtime.
  - 9d 1y ago
    But if this benchmark is right, then wasmtime is 5x faster than wasmi for it: https://github.com/khvzak/script-bench-rs https://github.com/khvzak/script-bench-rs
    - herobird 1y ago
      Wasmtime, being an optimizing JIT, usually is ~10 times faster than Wasmi during execution. However, execution is just one metric that might be of importance. For example, Wasmi's lazy startup time is much better (~100-1000x) since it does not have to produce machine code. This can result in cases where Wasmi is done executing while Wasmtime is still generating machine code. Old post with some measurements: https://wasmi-labs.github.io/blog/posts/wasmi-v0.32/ https://wasmi-labs.github.io/blog/posts/wasmi-v0.32/ Always benchmark and choose the best tool for your usage pattern.
      - 9d 1y ago
        That's a good point I didn't think about. I guess it's like v8 compared to quickjs. Anyway all this talk about wasm makes me want to write a scriptable Rust app!
  - phickey 1y ago
    Not sure how to help with this much information but I've built and run wasmtime on some pretty squalid architectures (xtensa and riscv32 microcontrollers among others) but the right collection of features might not be obvious. We can help you find the right configuration on the Bytecode Alliance zulip or the wasmtime issue tracker if you need it.

herobird 1y ago

Wasmi author here. Glad to see Wasmi being used in embedded contexts were it really shines. :) I just watched the demo video of Munal OS and am still in awe of all of its features. Really impressive work!

9d 1y ago
Yeah it's one of those projects were I'm so impressed that I'm saying nothing because there's nothing to say, it's just really impressive. I'm not sure what will come of this project, but it has a lot of potential to at least inspire other projects or spark important discussions around its innovations.
Gazoche 1y ago
Thank you! And thanks for making Wasmi, it's a really impressive project and it's the reason why I decided to go this whole WASM sandbox route (because I could embed it easily) :)
- herobird 1y ago
  Awww, makes me very happy to hear! :) Thank you!

phickey 1y ago

Wasmtime maintainer here - curious to hear what went wrong, I and several other users of wasmtime have production embeddings under no_std, so it should do everything you need, including building out WASI preview 2 support. You can find me on the bytecode alliance zulip if you need help.

lasiotus 1y ago
I'm not the OP, but I have a similar experience with Motor OS: wasmi compiles and works "out of the box", while wasmtime has a bunch of dependencies (e.g. target-lexicon) that won't compile on custom targets even if all features are turned off in wasmtime.
- 9d 1y ago
  But if this benchmark is right, then wasmtime is 5x faster than wasmi for it: https://github.com/khvzak/script-bench-rs https://github.com/khvzak/script-bench-rs
  - herobird 1y ago
    Wasmtime, being an optimizing JIT, usually is ~10 times faster than Wasmi during execution. However, execution is just one metric that might be of importance. For example, Wasmi's lazy startup time is much better (~100-1000x) since it does not have to produce machine code. This can result in cases where Wasmi is done executing while Wasmtime is still generating machine code. Old post with some measurements: https://wasmi-labs.github.io/blog/posts/wasmi-v0.32/ https://wasmi-labs.github.io/blog/posts/wasmi-v0.32/ Always benchmark and choose the best tool for your usage pattern.
    - 9d 1y ago
      That's a good point I didn't think about. I guess it's like v8 compared to quickjs. Anyway all this talk about wasm makes me want to write a scriptable Rust app!
- phickey 1y ago
  Not sure how to help with this much information but I've built and run wasmtime on some pretty squalid architectures (xtensa and riscv32 microcontrollers among others) but the right collection of features might not be obvious. We can help you find the right configuration on the Bytecode Alliance zulip or the wasmtime issue tracker if you need it.