-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[enhancement](compaction) Optimize compaction policy for empty rowsets #56173
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
[enhancement](compaction) Optimize compaction policy for empty rowsets #56173
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
|
run buildall |
TPC-H: Total hot run time: 34618 ms |
TPC-DS: Total hot run time: 189328 ms |
ClickBench: Total hot run time: 29.79 s |
|
run buildall |
TPC-DS: Total hot run time: 190655 ms |
ClickBench: Total hot run time: 30.64 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run cloud_p0 |
|
run p0 |
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
1 similar comment
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
dataroaring
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
#56173) When more than 5 consecutive empty rowsets are found and they account for over 30% of all input rowsets, prioritize handling empty rowsets
#56173) When more than 5 consecutive empty rowsets are found and they account for over 30% of all input rowsets, prioritize handling empty rowsets
When more than 5 consecutive empty rowsets are found and they account for over 30% of all input rowsets, prioritize handling empty rowsets