Repository navigation
perf(store): retain recent tree snapshots for read acquisition - #2861
Open
Mirko-von-Leipzig wants to merge 2 commits into
Open
Mirko-von-Leipzig wants to merge 2 commits into
Mirko-von-Leipzig wants to merge 2 commits into
Conversation
This branch has not been deployed
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
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.
Retains four recent tree generations in
RecentSnapshots. Readers look up the generation matching their SQLite transaction’s tip, so they can acquire a consistent view even after newer trees have been published. Acquired snapshots remain valid after cache eviction.This implements the snapshot-retention follow-up proposed in #2859 and reduces retries when the writer advances during read acquisition. The current write order still requires waiting when SQLite is ahead of tree publication. Retained generations keep tree caches and metadata alive and conservatively delay SQL history pruning; the capacity is fixed at four, including the latest generation.
Changelog