Replies: 1 comment
-
By default Wasmer allocates 4Gb+2Gb memory guard virtual memory in case the WebAssembly memory doesn't define a maximum, to make sure the compiled Wasm modules run at max speed, although it will be custom depending on the system. You can customize this behavior via Wasmer Tunables https://docs.rs/wasmer/3.1.0/wasmer/trait.Tunables.html |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to understand how much memory wasmer requires to run total. Not how much memory just the wasm code needs, but how much memory the entire runtime needs for the wasm code itself, for any guard pages, or anything else required.
For instance, wasmtime says that all linear memory regions are preceded by a 2gb guard region: https://docs.wasmtime.dev/security.html
Is this also true for wasmer? Do you need at least a 2gb guard region for any wasm vm instance?
I also see that wasmer has some settings to change guard page sizes:
https://docs.rs/wasmer/1.0.0-alpha01.0/wasmer/struct.Tunables.html
Is there some rule for the minimum size a guard page must be in order to appropriately secure the VM?
Beta Was this translation helpful? Give feedback.
All reactions