Skip to content

Compaction by tombstone ratio in simpledb #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 26, 2025
Merged

Conversation

thomasjungblut
Copy link
Owner

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.

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.
@sebheitzmann
Copy link
Contributor

Nice. I will be in holliday next week. So maybe not connected so much. Thanks

@thomasjungblut
Copy link
Owner Author

thomasjungblut commented Feb 14, 2025 via email

@thomasjungblut thomasjungblut merged commit 834dd0d into main Feb 26, 2025
4 checks passed
@thomasjungblut thomasjungblut deleted the compaction_ratio branch February 26, 2025 10:05
thomasjungblut added a commit that referenced this pull request Feb 28, 2025
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.

Co-authored-by: Thomas Jungblut <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants