perf(rust, python): add optimizer passes and change initial order #8811
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The stack optimizer passes expression from root to leafs.
That means that this expression:
lit(1) * lit(2) + col("a")
would be exposed to the optimizer in this order:
lit(1) * lit(2) + col("a")
lit(1) * lit(2)
lit(1)
lit(2)
col("a")
And that fused multiply add optimization already triggers on 1 before constant folding can be triggered on 2.
So this PR changes the initial traversal of the expressions so that the stack will first traversed in order
5, 4, .. 1
, meaning that smaller argument optimizations can be triggered first.This will increase the amount of passes we take, but hopefully the extra triggered optimizations will be worth it.