-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Fix](Top-N opt) evicting quering rowsets in prior to correct use_count #30904
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
Conversation
|
Thank you for your contribution to Apache Doris. |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 37484 ms |
TPC-DS: Total hot run time: 174687 ms |
ClickBench: Total hot run time: 31.15 s |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
TeamCity be ut coverage result: |
…nt (apache#102) This addresses the scenario where a rowset cannot be removed.
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 37066 ms |
TPC-DS: Total hot run time: 174371 ms |
ClickBench: Total hot run time: 31.34 s |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
TeamCity be ut coverage result: |
|
clang-tidy review says "All clean, LGTM! 👍" |
xiaokang
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run buildall |
TPC-H: Total hot run time: 41474 ms |
TPC-DS: Total hot run time: 180875 ms |
ClickBench: Total hot run time: 30.68 s |
|
TeamCity be ut coverage result: |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
…nt (apache#102) (apache#30904) This addresses the scenario where a rowset cannot be removed.
This addresses the scenario where a rowset cannot be removed.
Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...