Updates in P-Masstree #11
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
Use non-temporal stores for final commit stores Add some optimizations by using optimistic locking
1. Done for insert, lookup, scan 2. Still working for delete
1. Done for testing insert, lookup, delete, scan 2. Modified to use optimistic locking 3. Provide read-committed without using non-temporal stores
Closed
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.
The implementation of P-Masstree is updated to use optimistic locks for reading paths (get, scan, and tree traversals) instead of atomic snapshot techniques employed in the prior version. The original Masstree also employs optimistic locks, so these updates just result in making P-Masstree more faithfully follow the original way of implementation. Another benefit from this update is P-Masstree can provide read-committed without employing non-temporal stores since readers in P-Masstree never return data before in-progress writes to the same object are finished.