[EXPERIMENTAL] Prefetch Engine for AA hybrid stores#15
Open
sushantmane wants to merge 1 commit into
Open
Conversation
da33b22 to
6a3450d
Compare
99a6adb to
e5eda58
Compare
6a3450d to
7c4795d
Compare
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.
Introduce Prefetch Engine for AA hybrid stores
This PR introduces a prefetch engine for hybrid stores to hide latency when
fetching RMD and values for incoming keys from RocksDB for use in DCR.
Here's how it works:
to be processed in the following fashion:
We fire prefetch requests for Keys belonging to
RT-TPs in sequential order.Record processing for each
TPbegins withVT-TP-0. By the time we reachRT-TP-0, ideally, RMD and values for the keys will already be in memory.How was this PR tested?
WIP
Does this PR introduce any user-facing changes?