[ 
https://issues.apache.org/jira/browse/CB-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607186#comment-16607186
 ] 

Raphael commented on CB-13767:
------------------------------

Sorry, forgot to add this: Assuming you have all your plugins and platforms as 
dependencies in your package.json, do "npm install" once before "cordova 
prepare" (or whatever you run then). This will allow dpendencies to be 
installed once by npm and cordova will find them then. The only exceptions are 
dependencies that use a git URL as their spec.

> Huge performance issues moving from cordova 6.5 to 8 due to cordova-fetch
> -------------------------------------------------------------------------
>
>                 Key: CB-13767
>                 URL: https://issues.apache.org/jira/browse/CB-13767
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: cordova-lib
>            Reporter: Andrew Crites
>            Priority: Major
>         Attachments: image-2018-09-07-15-23-30-849.png, 
> image-2018-09-07-15-24-06-688.png
>
>
> This is for a project with a wide variety of plugins ... about 25. This may 
> be above average, but not extreme. I've updated the project from cordova 6.5 
> to cordova 8. Cordova 8 always uses {{cordova-fetch}} to install plugins, so 
> I can't opt out. Before, I was not using {{cordova-fetch}}.
> {code}
> $ time npx cordova@6.5 platform add ios
>   23.85s user 9.26s system 130% cpu 25.414 total
> $ time npx cordova@8 platform add ios --nosave
>   402.44s user 61.94s system 119% cpu 6:28.09 total
> {code}
> That takes over 15 times longer. {{--nosave}} was used since this is the 
> default behavior for 6.5.
> For subsequent installations using {{--save}} (or default) the performance is 
> still like this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to