dotnet restore performance problems
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
I recently converted a solution with around 65 C# projects, all in the new sdk-format, from nuget to paket. I used convert-from-nuget, resolved the detected conflicts and did a paket simplify. I also removed all but one version restriction.
- Paket.dependencies contains around 40 nuget packages
- frameworks are restricted to netstandard2.0, net47, netcoreapp2.0
- Storage is set to none.
- Paket version is 5.167.2
- Before building, i clean all obj and bin folders.
With nuget, a dotnet restore took around 9 seconds.
With paket, the dotnet restore takes around 1:30 min.
Is this expected or am i possibly doing something wrong?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported comparison between dotnet restore with NuGet and Paket on a solution of similar size, using the stated framework restrictions and package count. Investigate the restore path after convert-from-nuget and paket simplify; done means identifying whether the slowdown is expected or isolating a reproducible performance issue with a clear next step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100