-
Notifications
You must be signed in to change notification settings - Fork 2k
Even more improvements in memory utilization HashAggregationExec when spilling #8428
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
enhancementNew feature or requestNew feature or request
Description
Is your feature request related to a problem or challenge?
This task is related to #7858, to follow up with some issues we've found with HashAggregationExec.
Specific issue we found is that during spill HashAggregationExec will sort and spill aggregation buffer, while sorting it will allocate buffer as big as current aggregation state
This will make operator using (twice) more memory than already allocated by the memory manager.
We need to find a solution which would respect allocated memory limit
Some ides can be find in the #7858, more specific in comments:
- Improvements in HashAggregationExec when spilling #7858 (comment)
- Improvements in HashAggregationExec when spilling #7858 (comment)
- Improvements in HashAggregationExec when spilling #7858 (comment)
but we are open for other ideas as well
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request