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

PERF: NuGet Cloning operations are showing heavily in allocations during VS solution load #13647

Closed
ToddGrun opened this issue Jul 22, 2024 · 0 comments · Fixed by NuGet/NuGet.Client#5930
Assignees
Labels
Category:Quality Week Issues that should be considered for quality week Functionality:Restore Priority:2 Issues for the current backlog. Tenet:Performance Performance issues Type:Bug

Comments

@ToddGrun
Copy link

NuGet Product Used

Other/NA

Product Version

VS17

Worked before?

N/A

Impact

It's more difficult to complete my work

Repro Steps & Context

  1. Open VS, wait for everything to settle
  2. Start profiler
  3. Open vs-platform solution
  4. Wait for things to settle, stop profiler

*** interesting bit from memory profile ***
image

Verbose Logs

No response

@ToddGrun ToddGrun changed the title PERF: NnuGet Cloning operations are showing heavily in allocations during VS solution load PERF: NuGet Cloning operations are showing heavily in allocations during VS solution load Jul 22, 2024
@Nigusu-Allehu Nigusu-Allehu added Tenet:Performance Performance issues and removed Triage:Untriaged labels Jul 23, 2024
@nkolev92 nkolev92 added Functionality:Restore Priority:2 Issues for the current backlog. labels Aug 12, 2024
@nkolev92 nkolev92 self-assigned this Sep 27, 2024
@nkolev92 nkolev92 added the Category:Quality Week Issues that should be considered for quality week label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:Quality Week Issues that should be considered for quality week Functionality:Restore Priority:2 Issues for the current backlog. Tenet:Performance Performance issues Type:Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants