Should wasmtime serve -W max-memory-size=...
work as for wasmtime run
? I see that there is some plumbing that shares all the "common" run options, but I'm hitting an issue where this doesn't seem to be actually taking effect (cc @Alex Crichton @Dan Gohman )
it should in theory yeah, but I wouldn't be entirely surprised if there was a divergence
cool, I'll chase it down
one important difference between run/serve is that serve uses the pooling allocator by default
but that should be unrelated to max-memory-size
indeed
it looks like both run/serve are using StoreLimits
though and are calling the same method in src/common.rs
, so unsure :(
ah, well, the issue went away with a newer Wasmtime (I had v20 in my PATH by default)
it was still a documented option on that version but... all's well now shrug
Chris Fallin has marked this topic as resolved.
it might have been a refactoring between now-and-then that fixed this issue perhaps?
likely, yeah, not going to try to chase down exactly when it started working as long as it works now!
Last updated: Dec 23 2024 at 13:07 UTC