8000 Perfomance issue on module init for big apps caused by registerNgModuleType function. · Issue #39487 · angular/angular · GitHub
[go: up one dir, main page]

Skip to content
Perfomance issue on module init for big apps caused by registerNgModuleType function. #39487
Closed
@proofyman

Description

@proofyman

🐞 bug report

Affected Package

The issue is caused by package @angular/core

Is this a regression?

Don't know, seems like not.

Description

We have a big application with deep imports tree. There is function registerNgModuleType, that slow down application, depends on import count.

Problem is that its not depend on unique imports, just all imports, for every tree node down to leaf.

Function does nothing ( mb do something in compile time according to comment ), because it register modules, if them have ids. Modules in our app doesnt have them, no single module have id.

So function, that do nothing, slow down perfomance by 2 seconds for chrome, and 10s for ie11 on my pc. I just delete this function, and perfomance now is ok, and application fully workable.

🔬 Minimal Reproduction

Sorry, i cant add reproduction, because its requires enormous quantity of modules. I could generate them, if needed, but code clear enought to see the problem.

Anything else relevant?
Perfomance on navigation. All green fn blocks - registerNgModuleType and nested fns. There are a lot of calls, about 10k, i dont know. Each call takes 0.1ms, but all of them take 2s and do nothing.
image

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: coreIssues related to the framework runtimearea: performanceIssues related to performancecore: performancestate: has PR

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0