-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
executor: trace the memory usage of Selection executors #13927
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13927 +/- ##
===========================================
Coverage ? 80.2661%
===========================================
Files ? 483
Lines ? 121608
Branches ? 0
===========================================
Hits ? 97610
Misses ? 16273
Partials ? 7725 |
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.
~
/run-all-tests |
/run-unit-test |
1 similar comment
/run-unit-test |
All comments have been addressed, PTAL @SunRunAway @ichn-hu |
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
@SunRunAway, @XuHuaiyu, @wshwsh12, @ichn-hu, PTAL. |
LGTM, I guess I could borrow your test in my HashAgg memtracker! |
/run-all-tests |
@qw4990 merge failed. |
@SunRunAway, @ichn-hu, @XuHuaiyu, @wshwsh12, PTAL. |
/run-all-tests |
/run-all-tests |
/run-unit-test |
What problem does this PR solve?
Trace the memory usage of Selection executors and display the result in
Explain Analyze
.Wait for #13914.
What is changed and how it works?
Introduce a
memtracker
intoSelectionExec
and use it to trace the memory usage.Check List
Tests