question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compiler performance regression

See original GitHub issue

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 =

image

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:27 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
chuckjazcommented, Nov 30, 2016

it will be in 2.2.4 which should be released today or tomorrow.

0reactions
angular-automatic-lock-bot[bot]commented, Sep 10, 2019

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

IZ81241: COMPILE TIME PERFORMANCE REGRESSION
Compiler runs out of memory while compiling large program with optimization turned on. Local fix. Do not use optimization. Problem summary.
Read more >
Major Compile Performance Regression Swift 5.6
There seems to be a major compile speed regression when compiling postgres-nio using the latest Swift 5.6 Development toolchain.
Read more >
Performance regression with self-hosted compiler #12713
The self-hosted performance should be on-par with the stage1 compiler. ... As You can see, self-hosted is approximately 4 times slower overall, ...
Read more >
Performance regression ~30-40% with SSA optimizer
I'm wondering if you have ways/tools/expertise to pinpoint the source of such performance regression? Also I know about Intel vendors working with compiler...
Read more >
Compiler performance regression OTP 23.1+
I noticed a significant performance hit while compiling an application. E.g. for an application with ~50 dependencies, compiling just the ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found