-
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
make the memory tracing in HashAggExec
more accurate
#14705
Labels
epic/memory-management
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
sig/execution
SIG execution
type/enhancement
The issue or PR belongs to an enhancement.
Comments
55 tasks
let me fix it. |
Nice, thanks very much. If you have any problem or question, please feel free to discuss with us :D |
@tangwz Friendly ping~ |
Another case: The key of the aggregation map is a string, we should also track the memory usage when the |
@SunRunAway PTAL. |
Duplicate of #14103 |
17 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
epic/memory-management
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
sig/execution
SIG execution
type/enhancement
The issue or PR belongs to an enhancement.
Feature Request
Is your feature request related to a problem? Please describe:
A
memTracker
is used to trace memory consumed byChunks
inHashAggExec
, but in some cases(#14024), theaggPartialResultMapper
used to store intermediate results consumes a lot of memory but we don't trace it now.Please help us to make the memory tracing in
HashAggExec
more accurate by tracing all memory consumed by theaggPartialResultMapper
.If you are interested in this issue, welcome to join our SIG-EXEC channel to discuss it with us.
Thanks for your contribution:D
The text was updated successfully, but these errors were encountered: