Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
The expression id generations depend on a atomic long object internally, which will cause the performance drop dramatically in a multi-threading execution.
I'd like to create 2 sub tasks(maybe more) for the improvements:
1) Reduce the expression tree object creation from the aggregation functions (min/max), as they will create expression trees for each single row.
2) Remove the id property from the TreeNode API.
And remove the expression object creation as many as possible, where we have the expression evaluation. (I will create couple of subtask soon).