-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Expose remaining pooling allocator options as CLI flags #9256
Labels
good first issue
Issues that are good for new contributors to tackle!
Comments
alexcrichton
added
the
good first issue
Issues that are good for new contributors to tackle!
label
Sep 16, 2024
I'm tagging this as a "good first issue" and the basic task would be:
We don't have exhaustive tests for Wasmtime's CLI options at this time so it's ok to skip the tests for this at this time and just rely on code review to catch issues. |
Can I take this? |
Feel free! |
🤦 sorry @vHugoObject! I totally missed your comment before opening the PR. |
No problem at all, I have been too busy for this anyways.
…On Thu, Oct 10, 2024 at 14:35 Omar Jatoi ***@***.***> wrote:
🤦 sorry @vHugoObject <https://github.com/vHugoObject>! I totally missed
your comment before opening the PR.
—
Reply to this email directly, view it on GitHub
<#9256 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACEGOVS6TLKJ2OYTE6RRKMDZ23JHNAVCNFSM6AAAAABOJWBTWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVHA4TAMRQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 10, 2024
* Update `decommit_batch_size` type to `usize` * Add missing pooling options to `OptimizeOptions` * Add new pooling options to configuration * Add `max_memory_protection_keys` option also rename `memory_protection_keys` to `pooling_memory_protection_keys` * Add `total_gc_heaps` option * Add default options in comments
Landed in #9447, so I'm going to close this. Thkas @omarjatoi! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wasmtime's pooling instance allocator has a number of configuration options not all of which are reflected onto the CLI at this time around here. Ideally all of the pooling alloctator configuration options should be reflected on the CLI with a various
-O pooling-...
flag.The text was updated successfully, but these errors were encountered: