-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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: make memory tracing in ProjectionExec mo ... (#17109) #17118
executor: make memory tracing in ProjectionExec mo ... (#17109) #17118
Conversation
Signed-off-by: sre-bot <sre-bot@pingcap.com>
/run-all-tests |
@qw4990 Please resolve the conflicting files. |
Conflicts have been resolved, PTAL @SunRunAway @wshwsh12 |
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
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
/run-all-tests |
@sre-bot merge failed. |
/run-all-tests |
/merge |
/run-all-tests |
@sre-bot merge failed. |
/run-unit-test |
/run-integration-copr-test |
All checks have passed, PTAL @zz-jason |
cherry-pick #17109 to release-4.0
What problem does this PR solve?
Issue Number: close #16697
Problem Summary: make memory tracing in ProjectionExec more accurate
What is changed and how it works?
projectionWorker
may change the size of its input data chunk, but we don't trace this memory change.Check List
Tests
Release note
ProjectionExec
more accurate