Composer update takes ages

[motin]

Is it necessary to fetch the bower.json from every tag of the github repositories? Composer does that for custom VCS and that is fine I guess since that is only supported by root project. Can the assets be added to packagist package cache or similar instead?

The practical implications currently are that composer update takes ages. Requiring jquery without any version constraint will trigger 122 fetches of bower.json since there are 122 releases of jquery https://github.com/jquery/jquery/releases. Using a version constraint it will only fetch the relevant bower.json files but it still takes 1-10 minutes to run composer update, depending on one's internet connection.

[francoispluchino]

Because it's the native behavior of Composer. That is why I introduced more optimizations: the package lazy loading and the root filter import.

You can also read:

• FAQs: Why is Composer slow when the plugin retrieves the package definitions?
• FAQs: Why are the definitions from multiple versions of package retrieved to install?
• FAQs: Why are retrieved from all the version definitions of all packages to update?
• FAQs: How to reduce the number of requests for getting the package definitions?
• Issue Question: Performance improvements possible? #42
• Issue Memory Issues #43
• Issue Limit the import of versions of packages for a VCS Repository #44

And yes, the most effective optimization is for the root Composer package, with constraints. But if you find an even better solution, I'm interested.

[francoispluchino]

Of course, for the moment, the optimizations are only available for dev.

[aleksanderd]

I just updated to dev-master and the composer update still so slow :( What I need to do to enable all possible optimisations/caches/etc? I did fixes for versions already, so I see only one version for each package, but it re-retrivied every time I run composer update and it is slow :( Is it not possible to hard cache all what we retrivied already?

thnx

[francoispluchino]

@aleksanderd Read How to reduce the number of requests for getting the package definitions?

Regarding your questions about the optimization / cache, etc... read the comment above.

You have all the informations on the native behavior of Composer: what is achievable, what is not achievable, and how to do for drastically improve the performance of your project.

[francoispluchino]

The issue #52 improves significantly the performance for the update.