You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be great if we could easily make the resulting snapshot's size available. For the CLI tool, perhaps just logging it to stdout, but in the embedding API having an accessor for it would be great.
And I guess there are at least two different sizes to be had here: the size added to the wasm file, and the size of the instance Memory. The latter might be more important, since the former is easy to derive.
The text was updated successfully, but these errors were encountered:
We could certainly add some logging of this information, but it is also easy to get via wasm-objdump -h. Given that, do you still think it is worth adding?
It'd be great if we could easily make the resulting snapshot's size available. For the CLI tool, perhaps just logging it to stdout, but in the embedding API having an accessor for it would be great.
And I guess there are at least two different sizes to be had here: the size added to the
wasm
file, and the size of the instanceMemory
. The latter might be more important, since the former is easy to derive.The text was updated successfully, but these errors were encountered: