How we ended up rewriting NuGet Restore in .NET 9 - .NET Blog (devblogs.microsoft.com)

submitted 1 year ago* (last edited 1 year ago) by Kissaki@programming.dev to c/dotnet@programming.dev

1 comments fedilink hide all child comments

This first push resulted in NuGet Restore times being cut in half, which was a reasonable stopping point for our work. However, along the way, we realized that a more extensive rewrite could improve performance by a factor of 5x or more.

Written from the perspective of several team members, this entry provides a deep dive into the internals of NuGet, as well as strategies to identify and address performance issues.

you are viewing a single comment's thread
view the rest of the comments

[-] Kissaki@programming.dev 1 points 1 year ago

When an internal team at Microsoft—let’s call them TeamX—reached out to us because their NuGet Restore times had drastically increased to over 30 minutes

lol, 30 min restore, wtf

this post was submitted on 09 Apr 2025

5 points (85.7% liked)

.NET

1869 readers

1 users here now

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements
Rule 4: Submit the original source. If a post reports on something found on another site, submit the latter

Related communities

Wikipedia pages

.NET (open source & cross platform)
.NET Framework (proprietary & Windows-only)

founded 3 years ago

MODERATORS

erlingur@programming.dev

starman@programming.dev

Spyros@programming.dev