Speed up ops_log by storing up to 100 changes per repo file
#1395
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
This makes `ops_log` require I/O only once every 100 changes. Other improvement is that we store the update time for every change, that can now be returned in `ops_log` TODO in future PR: make the repo file store a configurable number of changes instead of hardcoding 100.
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 makes
ops_logrequire I/O only once every 100 changes.Other improvement is that we store the update time for every change, that can now be returned in
ops_logTODO in future PR: make the repo file store a configurable number of changes instead of hardcoding 100.