Ekleog commented on Issue #642:
So I'm not totally sure what exactly is wanted from this issue, but I've just published the wasmtime-async crate that probably handles this problem -- though not yet handling wasi, due to limitations in the API, though hopefully these will be fixed soon-ish with https://github.com/bytecodealliance/wasmtime/pull/1600.
If so, I've opened https://github.com/bytecodealliance/wasmtime/issues/1672 for suggesting inclusion and/or referring to it from wasmtime's docs, to see what happens :)
sunny-g commented on Issue #642:
@Ekleog url is missing the
/crates
path: wasmtime-async. Also, nicely done!
rrichardson commented on Issue #642:
@Ekleog - This is fantastic!
I will get started with it today.
rrichardson closed Issue #642:
Hello, apologies for asking this as an issue, but I'm not sure where else to ask questions of this nature.
Is it possible to deschedule and re-schedule running wasm tasks? I'd like to run dozens or hundreds of wasm programs in an app server of sorts, but running each in its own thread seems a tad excessive.
Is it possible to hand to running wasm code functions which are effectively async, and deschedule the wasm program while it is waiting on IO?
Ekleog edited a comment on Issue #642:
So I'm not totally sure what exactly is wanted from this issue, but I've just published the wasmtime-async crate that probably handles this problem -- though not yet handling wasi, due to limitations in the API, though hopefully these will be fixed soon-ish with https://github.com/bytecodealliance/wasmtime/pull/1600.
If so, I've opened https://github.com/bytecodealliance/wasmtime/issues/1672 for suggesting inclusion and/or referring to it from wasmtime's docs, to see what happens :)
alexcrichton commented on Issue #642:
I've opened https://github.com/bytecodealliance/rfcs/pull/2 for what it might look like supporting this in wasmtime itself, curious to hear what others think!
Last updated: Dec 23 2024 at 12:05 UTC