Degraded performance after upgrading to version Chocolatey CLI v2.0.0 #3183
Comments
|
Same here: |
|
While this may not help with the problem, I hope it highlights:
So be prepared for technical questions as we look at this more and more. |
|
We have found an area where we can improve the optimization of this and will be looking to release a pre-release version shortly for testing. I will update this issue when it happens so if you want to be notified, please subscribe to this issue. |
|
Having done some investigation on this issue, the problem stems from this issue within the Chocolatey.NuGet.Client assemblies. That issue will need to be addressed, and a new version of the Chocolatey.NuGet.Client assemblies brought into Chocolatey CLI to correct this problem. A PR will be raised, and the necessary changes made to Chocolatey CLI once a new version is released. |
In order to prevent a 1 second delay being imposed on each outgoing query, we need to make sure that an instance of a ChocolateySourceCacheContext is passed into every method that is called within the Chocolatey.NuGet.Client libraries. In order for this to work changes were needed to be made in the Chocolatey.NuGet.Client libraries to provide the overrides for all of these methods. This commit addresses issues that were reported with the 2.0.0 release of Chocolatey CLI, where performance of commands was significantly slower than on v1.4.0.
In order to prevent a 1 second delay being imposed on each outgoing query, we need to make sure that an instance of a ChocolateySourceCacheContext is passed into every method that is called within the Chocolatey.NuGet.Client libraries. In order for this to work changes were needed to be made in the Chocolatey.NuGet.Client libraries to provide the overrides for all of these methods. This commit addresses issues that were reported with the 2.0.0 release of Chocolatey CLI, where performance of commands was significantly slower than on v1.4.0.
In order to prevent a 1 second delay being imposed on each outgoing query, we need to make sure that an instance of a ChocolateySourceCacheContext is passed into every method that is called within the Chocolatey.NuGet.Client libraries. In order for this to work changes were needed to be made in the Chocolatey.NuGet.Client libraries to provide the overrides for all of these methods. This commit addresses issues that were reported with the 2.0.0 release of Chocolatey CLI, where performance of commands was significantly slower than on v1.4.0.
|
@gep13, thank you for the update. Out of curiosity, is there an ETA for this fix to be implemented and made available for everyone? Are we looking at a few days or weeks? Or will it possibly take a month or more? |
In order to prevent a 1 second delay being imposed on each outgoing query, we need to make sure that an instance of a ChocolateySourceCacheContext is passed into every method that is called within the Chocolatey.NuGet.Client libraries. In order for this to work changes were needed to be made in the Chocolatey.NuGet.Client libraries to provide the overrides for all of these methods. This commit addresses issues that were reported with the 2.0.0 release of Chocolatey CLI, where performance of commands was significantly slower than on v1.4.0.
In order to prevent a 1 second delay being imposed on each outgoing query, we need to make sure that an instance of a ChocolateySourceCacheContext is passed into every method that is called within the Chocolatey.NuGet.Client libraries. In order for this to work changes were needed to be made in the Chocolatey.NuGet.Client libraries to provide the overrides for all of these methods. This commit addresses issues that were reported with the 2.0.0 release of Chocolatey CLI, where performance of commands was significantly slower than on v1.4.0.
In order to prevent a 1 second delay being imposed on each outgoing query, we need to make sure that an instance of a ChocolateySourceCacheContext is passed into every method that is called within the Chocolatey.NuGet.Client libraries. In order for this to work changes were needed to be made in the Chocolatey.NuGet.Client libraries to provide the overrides for all of these methods. This commit addresses issues that were reported with the 2.0.0 release of Chocolatey CLI, where performance of commands was significantly slower than on v1.4.0.
|
@IFireflyl There will be a pre-release in the next couple of days for this. We will update this issue when that happens. |
|
if can help, checking the chocolatey GUI logs, we can find: i know the app is in Portuguese, but the log is in english. |
|
A new version of Chocolatey CLI (v2.1.0-alpha-20230608) has been released which aims to address this issue. You can find the release notes here: https://docs.chocolatey.org/en-us/choco/release-notes#alpha-20230608-june-8-2023 And the package here: https://community.chocolatey.org/packages/chocolatey/2.1.0-alpha-20230608 You should be able to upgrade to this package version using: If you could take this for a spin, and verify that the issue is now resolved, that would be very helpful. |
|
🎉 This issue has been resolved in version 2.1.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
Checklist
What You Are Seeing?
After upgrading Chocolatey to version 2.0 it is considerably slower when doing
outdatedorupgrade all -noop.=> choco 1.4 vs. choco 2.0
=> 4 sources configured, 20 packages installed.
=> choco 1.4 ~ 3 sec.
=> choco 2.0 ~ 97 sec.
Additional note: feeds are ProGet hosted, NuGet v2 feeds, LAN-type 1GBit-connection between demo host and Server, firewalls disabled during test.
What is Expected?
Performance should not be worse in the new version.
How Did You Get This To Happen?
I ran
choco outdatedon a demo system, with chocolatey 1.4 and chocolatey 2.0System Details
Installed Packages
Output Log
Additional Context
No response
The text was updated successfully, but these errors were encountered: