-
Notifications
You must be signed in to change notification settings - Fork 139
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
Pick the per-instance and global memory limits #341
Comments
I think @raulk had some thoughts on initial values here. |
For M1 (nv16), we are going with unlimited max pages given that the system can only run trusted logic via builtin system actors. However, it's not clear how many initial pages should be to avoid excessive memory expansion operations. Opened #369 to track that. @Stebalien will your benchmarks yield a good value for initial pages? For M2, there's a proposal here: filecoin-project/FIPs#317. |
Need to resurrect this issue for M2.1 (FEVM). In discussions over time we have settled on not charging for memory allocated, but rather for memory expansions. Finding the gas value/formula to charge per expansion will be subject of upcoming work, but for now we should at least set a max pages to a reasonable value (in the past we've discussed 64MiB, 256MiB, or 512MiB, IIRC). |
We're sticking with 2GiB for now. Pending FIP. |
Pick the correct per-instance and global memory limit.
The text was updated successfully, but these errors were encountered: