-
-
Notifications
You must be signed in to change notification settings - Fork 675
feat: enhance lowMemoryLimit to support larger than 64k memory limitation
#2910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: enhance lowMemoryLimit to support larger than 64k memory limitation
#2910
Conversation
LowMemoryLimit was originally introduced for embedded devices with very limited RAM for which even a single 64k bytes (single page) was not possible
This pr want to let this limitation available for some larger ram devices.
some rumtime like v8 will not allocate memory when memory grow. instead, they will allocate when memory is used.
for example, some embedden devices have 1MB ram, but still not enough to run multiple wasm together. it is good to use this option to limit ram usage less than e.g. 1.5 wasm pages.
This PR has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions!
This PR has been automatically closed due to lack of recent activity, but feel free to reopen it as long as you merge in the main branch afterwards.
1e7c006 to
3988dd9
Compare
For the record, we should opt to use custom-page-sizes when support is added in Binaryen.
This PR want
lowMemoryLimitto accept memory limitation which more than 64k but cannot be divisible by 64k.It can help generated wasm module with fine-grained memory management.