dotnet restore: Slow restore performance
See original GitHub issueWith nuget.exe
it was possible to set NUGET_CERT_REVOCATION_MODE
to offline
This environment variable seems to not have an effect on dotnet restore
.
Is there any possibility to turn off those revocation checks for dotnet restore
.
As our CI is running in network with very limited network access, restoring NuGet dependencies is dramatically slowed down by this missing configuration possibility.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:11 (4 by maintainers)
Top Results From Across the Web
DotNet core slow restore : r/docker
DotNet core slow restore. Hello,. recently I'm facing a increase on the build time (+5 minutes from initial ~1 minute) when doing ....
Read more >dotnet restore incredibly slow inside docker-compose build
If I cd into the directory and run dotnet restore , the packages are restored very quickly without any problems. But when it...
Read more >NuGet Restore takes 25% of the time of my build
The full task takes 1 minute, 23 seconds. As I've pointed out, of this entire time, it appears just starting the NuGet executable...
Read more >NuGet restore extremly slow : RIDER-43960 - YouTrack
After upgrading from 2019.3.1. to any of the 2020 versions NuGet restore seems to be extremly slow. Solutions with 1 project; and the...
Read more >Solving flaky dotnet restore issue only on Docker
When I build a Dockerfile, at the part of the dotnet restore I encountered this issue. However, On my colleague's PC, it works...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Signed package verification was not enabled on Linux until .NET SDK 5., so revocation checks related to NuGet signed package verification cannot be the reason for slow performance under .NET Core SDK 3.1.
NUGET_CERT_REVOCATION_MODE
won’t have any effect under .NET Core SDK 3.1.As a side note, NuGet signed package verification was temporarily disabled by default on Linux with .NET SDK 5.0.202.
If this is indeed a problem experienced with .NET Core SDK 3.1, then retitle/reword this issue as slow restore performance; signed package verification and revocation checks are unrelated.
cheers => https://github.com/NuGet/Home/discussions/12028