-
Notifications
You must be signed in to change notification settings - Fork 905
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
Improve overall execution time when performing the choco upgrade all
command
#3231
Comments
This optimizes the flow of the upgrade command. First, it uses the list of locally installed package from the if all is specified check, instead of throwing that away. Then, it will re-use the list for each package upgrade attempt, only refreshing the list when a package upgrade/install is attempted. This speeds up upgrade all runs, especially when a large (200+) number of packages are installed.
But the issue was 'resolved' in v2.1.0. 🙄 |
I think you might be referring to this issue: Which was indeed fixed in v2.1.0. That issue was the result of a imposed 1 second delay on each HTTP request that was made by Chocolatey CLI, which had an impact on pretty much all the commands that Chocolatey CLi has. This issue that @TheCakeIsNaOH has raised is specifically for the |
This optimizes the flow of the upgrade command. First, it uses the list of locally installed package from the if all is specified check, instead of throwing that away. Then, it will re-use the list for each package upgrade attempt, only refreshing the list when a package upgrade/install is attempted. This speeds up upgrade all runs, especially when a large (200+) number of packages are installed.
Add integration tests that ensure we don't run the local package listing more than once per upgraded package.
This optimizes the flow of the upgrade command. First, it uses the list of locally installed package from the if all is specified check, instead of throwing that away. Then, it will re-use the list for each package upgrade attempt, only refreshing the list when a package upgrade/install is attempted. This speeds up upgrade all runs, especially when a large (200+) number of packages are installed.
Add integration tests that ensure we don't run the local package listing more than once per upgraded package.
(#3231) Don't refresh local package info during upgrade no-ops
choco upgrade all
command
* release/2.2.0: (21 commits) (doc) Update to indicate new package version used (maint) Add helper to split on max line lengths (#3281) Add validation for cache folder permissions (#3264) Update to latest Chocolatey.NuGet.Client (#3264) Ignore lock folders in cache directories (#3186) Remove easter egg (doc) Improve error message for defaultPushSource (tests) Clear HTTP Cache before getting packages (#3258) Expand logging for nuget resources errors (maint) Set file encoding to include BOM (#3237) Reduce number of queries for dependencies (#3231) Add tests to ensure package listing (maint) Remove unnecessary using statements (#3231) Don't refresh local package info during upgrade no-ops (build) Update to latest recipe package (doc) Minor corrections to wording (#3242) Add a script to run Authenticated tests (#3242) Attempt default credentials for sources (maint) Fix incorrect naming style uses (doc) Apply scripting best practices to output ...
🎉 This issue has been resolved in version 2.2.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
Checklist
Is Your Feature Request Related To A Problem? Please describe.
When a large number of packages (e.g. 300+) are installed on Chocolatey CLI v2.x, the
choco upgrade all
command takes quite a bit longer to run than it did on v1.4.0One large contributor to this is that Chocolatey now gets a list of all installed packages before every upgrade check, instead of only refreshing the list when a package upgrade happens. This check can take a while when a large number of packages are installed.
Describe The Solution. Why is it needed?
Chocolatey should only get the list of all installed packages when required, instead of before every package outdated check.
Additional Context
No response
Related Issues
The text was updated successfully, but these errors were encountered: