-
Notifications
You must be signed in to change notification settings - Fork 31
lib: enable disk based caching #393
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
Merged
Merged
Conversation
This file contains hidden or 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
BREAKING CHANGE: use 'computer.db.wallet' instead of 'computer.wallet'
Closed
ltardivo
reviewed
Jun 13, 2025
ltardivo
reviewed
Jun 13, 2025
* Grant patent to any user of this code * Explain payment terms * Make everything MIT licensed
…monorepo into add-hd-cache-2
ltardivo
approved these changes
Jul 10, 2025
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 PR will enable disk based caching for on-chain objects. These Objects are now cached on disk once they are computed for the first time. Every subsequent access is directly from disk, so that every step in the computation only needs to be performed once.
While synchronizing to an object, all objects are cached in memory (this was introduced in a previous PR) so that they can be accessed up even faster. Once the sync process completes the newly computed on-chain objects on the blockchain are flushed to disk.
BREAKING CHANGE: use 'computer.db.wallet' instead of 'computer.wallet'