Clean up storage constants and remove 32GB limitation #2289
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This removes outdated constants in the `storage` module and removes an obsolete element from the II stable memory header. The 32GB memory limit is dropped as well. Due to limitations of the memory manager (to manage at most 256GB given the bucket size used) we still maintain a reserve of ~144GB stable memory that cannot be used for identities.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This removes outdated constants in the
storagemodule and removes an obsolete element from the II stable memory header. The 32GB memory limit is dropped as well. Due to limitations of the memory manager (to manage at most 256GB given the bucket size used) we still maintain a reserve of ~144GB stable memory that cannot be used for identities.