Prime offset of anti-cache with timestamps #172
Merged
Conversation
This file contains 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
…threshold for now.
What a bug!!! We do not need to scan the specific block when calculating tupleID in LRU.
Conflicts: src/ee/anticache/EvictionIterator.cpp src/frontend/edu/brown/hstore/AntiCacheManager.java
…very block at once.
apavlo
added a commit
that referenced
this pull request
Aug 30, 2014
Prime offset of anti-cache with timestamps
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 is a change of the sampling strategy in anti-cache with timestamps.
Now we use a prime offset that is relatively-prime to the number of tuples in the block, instead of using rand and %.