Ruby: Eliminate unnecessary recursion through RealNode#7141
Merged
Conversation
ad9035c to
ed883a8
Compare
ed883a8 to
e7b0910
Compare
Contributor
Author
|
Here are some performance numbers: Before: After |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When investigating the (minor) performance regression introduced by #7098, I realized that we have unnecessary recursion through the
newtypeconstructorRealNodein the synthesis framework. This PR splits upRealNodeintoRealNodeRefandSynthNodeRef, where the former is restricted to real nodes (no recursion), and the latter to synthesized nodes (recursion). This makes a big difference because the recursion inSynthesis::child/3is non-linear.The changes in this PR will conflict with #7098, so I suggest we rebase that PR once this PR is merged, and then rerun performance checks.