-
Notifications
You must be signed in to change notification settings - Fork 557
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
feature_request: increase STORAGE_SIZE_LIMIT #1664
Comments
@FrederikBolding Any updates/information on this ? |
@martines3000 Sorry for the radio silence, we are still discussing internally. I'll try to get an update for you soon! |
@FrederikBolding Any new updates/information on this ? |
@martines3000 Sorry for the lack of response, we aren't sure yet whether we can increase the storage limit much more. It also feels like a slightly hacky solution. Would an API like the one I suggested in #1778 be useful to your use-case? I'm wondering if you could bundle the auxiliary files needed for the snaps and lazy load them as needed? |
Closing this as this is no longer an issue now that we have File API support. Please feel free to re-open if you think File API support does not address your use case. |
Increase the STORAGE_SIZE_LIMIT to 200MB (209715200 bytes).
This would allow snaps that require larger datasets to load them on the first startup (fetch from remote server) and store them locally. This dramatically reduces the snaps bundle size and improves the cold start (wake up) times.
We are experiencing this issue because we are using Polygon ID circuits (the size is approximately 127 Mb).
This would resolve our problem.
The text was updated successfully, but these errors were encountered: