mirror of
https://github.com/versity/scoutfs.git
synced 2026-02-07 19:20:44 +00:00
3f812fa9a7
The first pass at compaction just kicked a thread any time we added a segment that brought its level's count over the limit. Tasks could create dirty items and write level0 segments regardless of the progress of compaction. This ties the writing rate to compaction. Writers have to wait to hold a transaction until the dirty item count is under a segment and there's no level0 segments. Usualy more level0 segments are allowed but we're aggressively pushing compaction, we'll relax this later. This also more forcefully ensures that compaction makes forward progress. We kick the compaction thread if we exceed the level count, wait for level0 to drain, or successfully complete a compaction. We tweak scoutfs_manifest_next_compact() to return 0 if there's no compaction work to do so the the compaction thread can exit without triggering another. For clarity we also kick off a sync after compaction so that we don't sit around with a dirty manifest until the next sync. This may not be wise. Signed-off-by: Zach Brown <zab@versity.com>