-
Notifications
You must be signed in to change notification settings - Fork 170
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
Readme: should highlight that improvement only without local composer cache #196
Comments
What kind of sentences do you agree with? |
Something in the vicinity of
maybe? That would be more then sufficient in my eyes. |
don't mean to derail here, but I'm just curious, if this package is as useful as I feel it is (been using it for 2 years+ now and see no reason to stop), why hasn't Composer implemented this functionality as part of the core Composer installer? o_O |
Is it true that there's no benefit when packages are cached? The animated gif on the homepage (of the Laravel install) shows packages being loaded from cache, which seems somewhat deceptive if true. It also looks like the Composer plugin does other stuff (such as with dependency sorting) that might have performance implications even with cached packages. |
Ah... I just noticed that when Prestissimo is installed, Composer always claims packages are "loading from cache" even on a cold cache. That seems like its own point of confusion, but at least explains the discrepancy in the readme. |
Note: The readme already states that the plugin speeds up the download of packages.
Though this fact should be pressed harder to ensure that ppl. who just fly over the description get the point that it only improves the download-speed (pre-fetches packages in parallel).
Was about to create an actual "issue" where there is none.
If the cache is already available (all packages available in composer-cache) the plugin does not give any improvements.
Though it would probably nice if it would actually override the installation-process and unpack the cached packages with multiple threads ;)
The advantage in my specific case is very limited as my cache is preserved and only purged on a monthly basis.
The text was updated successfully, but these errors were encountered: