-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](memory) Fix query mem tracker log when destruction not equal to 0 #34901
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. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 41841 ms |
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 186706 ms |
ClickBench: Total hot run time: 30.61 s |
TPC-H: Total hot run time: 41013 ms |
TPC-DS: Total hot run time: 186551 ms |
ClickBench: Total hot run time: 30.91 s |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
wangbo
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
|
comment run performance |
1 similar comment
|
comment run performance |
3f45e79 to
f969c4b
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
Proposed changes
Fix query mem tracker log when destruction not equal to 0
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...