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
According to https://v8.dev/blog/4gb-wasm-memory, the v8 engine (used by envoy to run WASM filters) implements wasm32, which has 4gb as the total usable memory.
This however doesn't necessarily mean that memory allocation has a limit of 4gb. Is there any cap on how much memory can be allocated apart from the aforementioned hard limit? Any clarification would be much appreciated!
The text was updated successfully, but these errors were encountered:
pranav-bhatt
changed the title
[Question] Is there a memory allocation within a WASM extension using Envoy (using V8 runtime)?
[Question] Is there a memory allocation limit within a WASM extension using Envoy (using V8 runtime)?
Sep 8, 2021
I believe that 64bit support has been implemented, reference the following page to see that it "It provides no new instructions, but instead extends the currently existing instructions to allow 64-bit indexes."
If this is satisfactory, I would like to close this issue.
saurabh100ni
added
issue/stale
Issue has not had any activity for an extended period of time
and removed
issue/stale
Issue has not had any activity for an extended period of time
labels
Nov 9, 2023
According to https://v8.dev/blog/4gb-wasm-memory, the v8 engine (used by envoy to run WASM filters) implements
wasm32
, which has 4gb as the total usable memory.This however doesn't necessarily mean that memory allocation has a limit of 4gb. Is there any cap on how much memory can be allocated apart from the aforementioned hard limit? Any clarification would be much appreciated!
The text was updated successfully, but these errors were encountered: