angular: Compiler performance regression
I’m submitting a … (check one with “x”)
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior After updating to 2.2.1 or 2.2.3, the a mid-sized app (~50k LOC or so) takes over 90 seconds to bootstrap. In 2.2.0, the same app bootstraps in under 5 seconds.
Expected behavior Time to bootstrap should not take this long.
Minimal reproduction of the problem with instructions The app is using the JIT compiler and includes approximately 30 app NgModules, built with Webpack. It is a sizable enough codebase that makes reproducing in the small difficult.
I have captured a CPU profile from Chrome, screenshot attached below. The green lines are angular. This profile runs 90 seconds.
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
- Angular version: 2.2.1 and 2.2.3
- Browser: all (tested latest Chrome, Firefox, Safari across different operating systems); tested with devtools open and closed
-
Language: TypeScript 2.0.9
-
Node (for AoT issues):
node --version
=
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 27 (10 by maintainers)
Commits related to this issue
- fix(compiler): fix performance regression caused by 5b0f9e2 Fixes #13146 — committed to chuckjaz/angular by chuckjaz 8 years ago
- fix(compiler): fix performance regression caused by 5b0f9e2 Fixes #13146 — committed to alxhub/angular by chuckjaz 8 years ago
- fix(compiler): fix performance regression caused by 5b0f9e2 Fixes #13146 — committed to alxhub/angular by chuckjaz 8 years ago
- fix(compiler): fix performance regression caused by 5b0f9e2 Fixes #13146 — committed to angular/angular by chuckjaz 8 years ago
it will be in 2.2.4 which should be released today or tomorrow.