Paket is very slow with ASP.NET Core 2
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Performance is suboptimal when paket is used with ASP.NET Core 2. Just wondering if that is because of microsoft.aspnetcore.all metapackage or issue is the same as in #2827?
Repro steps
-
dotnet new webapi -
download paket.exe (ver 5.153.0), save it to
./paketdirectory -
.\.paket\paket.exe convert-from-nugettakes ~ 5 minutes -
.\.paket\paket.exe updatetakes minutes -
.\.paket\paket.exe add xunittakes minutes
Repro is available here
Expected behavior
It is expected to be much faster.
Actual behavior
Steps 3..5 should not take minutes, but rather seconds. Console output can be observed in my twitter.
Known workarounds
No any.
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 with the linked skalinets/paket-issue reproduction and run paket.exe convert-from-nuget, update, and add xunit using Paket 5.153.0. Compare the command timings and console output with the reported behavior, and review issue #2827 for related investigation. Done means identifying and addressing why these ASP.NET Core 2 operations take minutes rather than seconds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100