[Backport] [38.0.0] perf: Interval tree for managing segment metadata in memory - #19851
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Segment metadata stored in memory of the Historicals, is used when looking up segments that match an interval for query and segment loading purposes. Currently this is a serial scan that goes through all segments metadata in ascending start time order to find matching segments. This changes introduces an Interval Tree as a more efficient way to store segment metadata in memory, to speed up searches for segments, and cut down search times from O(n) to O(logn). Changes: - Add IntervalTreeMap - Add SegmentTimelineConfig to enable fastIntervalSearch - Update SegmentManager and VersionedIntervalTimeline to use IntervalTreeMap when enabled - Add tests (cherry picked from commit 452b15b)
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
{
"backport_issue": "19850",
"message": "Backport for #19850"
}