[Transforms] Performance improvements in the binder.#8899
Merged
Conversation
Contributor
|
👍 |
1 similar comment
Member
|
👍 |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
This extracts logic from
computeTransformFlagsForNodefor switch cases that use properties onNodesubtypes. This allows NodeJS (or other hosts) to make deoptimization decisions for each branch rather than for the entirecomputeTransformFlagsForNodefunction which reduces bind time by 10-14% depending on scenario when compared to the "transforms" branch.This also manually inlines the
updateTransformFlagsfunction as it was too polymorphic to be properly inlined.