Compaction by tombstone ratio in simpledb #46
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 commit introduces a new compaction kind that will compact sstables when they have more than 20% of their keys tombstoned. This should save space when preserving them, as a later compaction can clean them up again. This trades-off available disk bandwidth and CPU with disk space.
cc @sebheitzmann I think I have to add a few more tests, but it seems to certainly fix the regression test from the previous PR.