Skip to content
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

Very slow "dotnet restore" in 9.0.200 or higher version #47784

Closed
tresoldigiorgio opened this issue Mar 21, 2025 · 3 comments
Closed

Very slow "dotnet restore" in 9.0.200 or higher version #47784

tresoldigiorgio opened this issue Mar 21, 2025 · 3 comments
Assignees
Milestone

Comments

@tresoldigiorgio
Copy link

The "restore" command is very slow in version 9.0.200 or higher.

I've created a simple project with only one dependency to my other nuget package and launched
dotnet restore --interactive --force --no-cache

in 9.0.101 or 102 the command is very fast (2 seconds) but in 9.0.200 or 202 (1:41 minute) is extremely slow and cunsumes large amount of ram (8GB).

Image

this is my csproj

`

<PropertyGroup>
    <TargetFramework>net9.0</TargetFramework>
</PropertyGroup>

<ItemGroup>
    <PackageReference Include="Nuvyta.SDK.App.Manager" Version="4.3.*" />
</ItemGroup>

`

this is the log by versions

101.log
102.log
200.log
202.log

this is my project dependencies

dependencies.txt

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-NetSDK untriaged Request triage from a team member labels Mar 21, 2025
@marcpopMSFT marcpopMSFT self-assigned this Mar 25, 2025
@marcpopMSFT
Copy link
Member

@aortiz-msft @nkolev92 Since this is restore, I have to assume it's nuget related. Should we have them open an issue there?

@marcpopMSFT marcpopMSFT added this to the Discussion milestone Mar 26, 2025
@marcpopMSFT marcpopMSFT removed the untriaged Request triage from a team member label Mar 26, 2025
@nkolev92
Copy link
Contributor

nkolev92 commented Mar 26, 2025

Yes.

I'm guessing it's the same root cause as NuGet/Home#14147, which is awaiting release in April.

cc @jeffkl

@tresoldigiorgio Do you have latest Visual Studio? Can you try 17.13's latest VS version?
Run msbuild /t:restore and it's the same as dotnet restore except it'll use the toolset that ships with VS.

It should have the fix.

@tresoldigiorgio
Copy link
Author

I don't use Visual Studio but Rider.
The big problem is azure devops builder for me

Image

I will follow nuget issue for resolution. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants