I recently tried to use the Wizer tool to pre-initialize the image-classification benchmark in the sightglass repository. While I was able to read in the mobilenet files, I was not able to call the wasmtime_wasi_nn implementations of wasi_nn:load and wasi_nn::init_execution_context in the wizer.initialize function because it seems like those two functions keeps state on the host (self.graphs and self.executions) that are lost in the wizened module. Is this correct, and if so would it theoretically be possible to keep that state in the Wasm module instead to make wasi_nn more Wizer-friendly? This isn't a feature request, but more out of curiosity.
When you say keep state in the wasm module do you mean on the guest side?
Last updated: Dec 23 2024 at 12:05 UTC