-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
@nestjs/core version 6.6.2-6.6.4 bootstrap ApplicationModule dependencies initialized very slow #2865
Comments
Eventually your service is up, and mine is waiting forever. |
@Jimmysh I just publish 6.6.5 version that should solve performance issues. Can you take a look and let me know if you still face any problems? |
@kamilmysliwiec Thanks |
I know this issue was marked closed but it still exist.....I am having the same problem and none of the suggestion works..I am using ver nest/core, nestjs/common and nestjs/graphql-express ver 6.8.5 with nestjs/grapql 6.5.3. If I leave it, in about 4 hours(yep) it will complete the startup with one of the modules taken all that time to start...I am also using the latest kit with tsc-watch |
@aliantjamaica Could you provide a minimal reproduction repository of the described behavior? |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug Report
Current behavior
version 6.6.1
[Nest] 11506 - 2019-09-03 12:12:28 PM [NestFactory] Starting Nest application...
[Nest] 11506 - 2019-09-03 12:12:28 PM [InstanceLoader] ApplicationModule dependencies +232ms
version 6.6.4
[Nest] 11648 - 2019-09-03 12:16:28 PM [NestFactory] Starting Nest application...
[Nest] 11648 - 2019-09-03 12:16:55 PM [InstanceLoader] ApplicationModule dependencies initialized +27575ms
Input Code
Expected behavior
Possible Solution
It will more slower when add more global modules.
cpuprofile
https://raw.githubusercontent.com/Jimmysh/nest/img/CPU-20190903T122636.cpuprofile
Environment
The text was updated successfully, but these errors were encountered: