You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
alamb
changed the title
Improvements in memory utilization HashAggregationExec when spilling
Even more improvements in memory utilization HashAggregationExec when spilling
Dec 5, 2023
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 statehttps://github.com/apache/arrow-datafusion/blob/7acd8833cc5d03ba7643d4ae424553c7681ccce8/datafusion/physical-plan/src/aggregates/row_hash.rs#L672
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:
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
The text was updated successfully, but these errors were encountered: