Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perf(ivy): do not use spread operations in styling #29795

Closed
wants to merge 1 commit into from

Conversation

matsko
Copy link
Contributor

@matsko matsko commented Apr 9, 2019

While investigating styling performance regressions, it was discovered
that a single fn(...args) operation was causing a performance hit
because the generated es5 __spread operation uses [].concat and
reads from the arguments values (which are not very efficient). This
patch changes that around to use fn.apply instead.

While investigating styling performance regressions, it was discovered
that a single `fn(...args)` operation was causing a performance hit
because the generated es5 `__spread` operation uses `[].concat` and
reads from the `arguments` values (which are not very efficient). This
patch changes that around to use `fn.apply` instead.
@matsko matsko requested a review from a team as a code owner April 9, 2019 21:11
@matsko matsko added action: merge The PR is ready for merge by the caretaker target: major This PR is targeted for the next major release labels Apr 9, 2019
@IgorMinar IgorMinar closed this in 675f390 Apr 10, 2019
@kara kara added the comp: ivy label Apr 10, 2019
@ngbot ngbot bot added this to the needsTriage milestone Apr 10, 2019
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
While investigating styling performance regressions, it was discovered
that a single `fn(...args)` operation was causing a performance hit
because the generated es5 `__spread` operation uses `[].concat` and
reads from the `arguments` values (which are not very efficient). This
patch changes that around to use `fn.apply` instead.

PR Close angular#29795
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants