Skip to content

Reconsider Wasmtime's allocation strategy "max table elements" config option #2127

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.

Sign up for GitHub

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

Jump to bottom
Open
Stebalien opened this issue Apr 8, 2025 · 0 comments
Open

Reconsider Wasmtime's allocation strategy "max table elements" config option #2127

Stebalien opened this issue Apr 8, 2025 · 0 comments
Labels
Topic: Gas and limits Topic: User Wasm User-deployable Wasm Actors

Comments

@Stebalien
Copy link
Member

We currently use the default of 20k but it sounds like that reserves enough memory for 20k elements up-front even if they aren't used, which is something we should charge for in our memory accounting logic. We currently charge for table use as they're used.
@Stebalien Stebalien added Topic: Gas and limits Topic: User Wasm User-deployable Wasm Actors labels Apr 8, 2025
@github-project-automation github-project-automation bot moved this to 📌 Triage in FilOz Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Topic: Gas and limits Topic: User Wasm User-deployable Wasm Actors
Projects
FilOz
Status: 📌 Triage
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Stebalien