Repository navigation
Conversation
RFC: Optimize MarkRanges by using devector over deque
Member
Author
|
Backporter: CI failures at e93b59b Failed checks:
Unrelated to this PR: The PR only swaps the MarkRanges container from deque to devector; the failures are a Hybrid-table reload problem from an existing test, a known flaky ZooKeeper DROP_RANGE error, and infrastructure jobs.
|
This branch has not been deployed
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
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 of ClickHouse#86933
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Improves performance of fast queries with lots of parts in table (by optimizing
MarkRangesby usingdevectoroverdeque) (ClickHouse#86933 by @azat)