Add benchmark for VersionedIntervalTimeline #8161
Merged
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.
Benchmark for VersionedIntervalTimeline introduced in #7547 (comment).
Description
The primary purpose of this benchmark is to measure how much slower VersionedIntervalTimeline is with segment lock than with timeChunk lock.
Data setup
A synthetic segments were created to emulate the usual compaction scenario where initial segments are created and then they got compacted while new segments are appended. The benchmark first generates
numInitialRootGenSegmentsPerInterval
segments per interval. Then, it generatesnumInitialRootGenSegmentsPerInterval * COMPACTED_SEGMENTS_RATIO_TO_INITIAL_SEGMENTS
compacted segments which overwrites the segments of the previous generation. It also generates new appending segments. This can be repeated more than once based onnumNonRootGenerations
.This PR has: