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

Incredibly slow install #1320

Closed
2 tasks done
ggrimbert opened this issue Oct 1, 2019 · 9 comments
Closed
2 tasks done

Incredibly slow install #1320

ggrimbert opened this issue Oct 1, 2019 · 9 comments
Labels
state:wont-fix Won’t be fixed with a clearly stated reason

Comments

@ggrimbert
Copy link

ggrimbert commented Oct 1, 2019

Hi,

I am experiencing some problems with the last version of parse dashboard. The issue is that the npm install goes from 1 minute to 15.

With the version 1.2.0; npm install take 40 seconds with the dependencies below; but with the 2.0.3 version, it takes more than 15 minutes.
It seems to hang on two tasks :

  • npm timing stage:loadIdealTree
  • npm timing action:extract

Here are the full logs for the slow install.
npmInstallParse.txt

I can assure you that our internal repository doesn't slow down the network.

  • You're running version >=2.3.2 of Parse Server.

  • You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Ubuntu 16.04; node 8.11

Steps to reproduce

Use these dependencies :

"dependencies": {
    "express": "^4.15.3",
    "graphql": "14.5.3",
    "node-schedule": "^1.3.2",
    "parse-dashboard": "2.0.3",
    "parse-server": "3.9.0"
  },
  "devDependencies": {
    "tslint": "^5.10.0",
    "typescript": "3.5.3"
  }

Logs/Trace

08:24:48 npm http fetch GET 200 https://nexusm-repo-mob.apps.eul.sncf.fr/repository/npm-groupeaes/cross-fetch 184ms
08:32:27 npm info lifecycle codemirror-graphql@0.6.12~prepack: codemirror-graphql@0.6.12
08:32:27 npm info lifecycle codemirror-graphql@0.6.12~postpack: codemirror-graphql@0.6.12
08:32:27 npm timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 474675ms
08:32:27 npm timing stage:loadIdealTree Completed in 475124ms
08:32:28 npm timing stage:generateActionsToTake Completed in 510ms
[...]
08:32:41 npm http fetch GET 200 https://nexusm-repo-mob.apps.eul.sncf.fr/repository/npm-groupeaes/aws-sdk/-/aws-sdk-2.539.0.tgz 11225ms
08:40:03 npm timing action:extract Completed in 454523ms
08:40:05 npm timing action:finalize Completed in 1431ms
08:40:07 npm timing action:refresh-package-json Completed in 1900ms
@davimacedo
Copy link
Member

I've just installed the dependencies in 20s:

added 737 packages from 1671 contributors in 21.253s

Can you share more details about your environment?

@ggrimbert
Copy link
Author

We use Jenkins to install the dependencies, we don't have more informations about this environment.

@GSZS
Copy link

GSZS commented Oct 3, 2019

I also have the same situation in version 2.0.3, the installation takes a lot of time

@ggrimbert
Copy link
Author

I don't know how but using an older version of npm the install is really faster

@dplewis
Copy link
Member

dplewis commented Oct 3, 2019

It might come from puppeteer (used for testing) downloads chromium. You can use an environment variable to skip downloading it.

https://github.com/GoogleChrome/puppeteer/blob/v0.10.2/docs/api.md#environment-variables

PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true npm install

@ggrimbert
Copy link
Author

There's no trace of puppeteer in the install logs

@davimacedo
Copy link
Member

Could you guys share the versions of npm and node.js that you are currently using?

@ggrimbert
Copy link
Author

We use node v8.16.1; with npm v6.4.1
It's the version 4.6.1 that makes ths install faster

@stale
Copy link

stale bot commented Nov 22, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label Nov 22, 2019
@stale stale bot closed this as completed Nov 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:wont-fix Won’t be fixed with a clearly stated reason
Projects
None yet
Development

No branches or pull requests

4 participants