[C#] Limit number of preloaded pages during recovery#292
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently we load all log pages (from headAddress to untilAddress) of a checkpoint into main memory part of hybrid log during recovery. This can take time to load, and keeps the database inaccessible until recovery is complete. Users can instead preload only a few pages (or no pages) into memory during recovery. This allows us to declare the key-value store ready for operation immediately after loading the hash table in memory and completing the (usually short) UNDO part of recovery.
To reduce the time taken to UNDO, users can take a sequence of [hlog checkpoint, index checkpoint, hlog checkpoint]. This can reduce the number of operations in flight that need to be checked for undo.
Usage:
store.Recover(int numPagesToPreload = -1)