-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Reduce lsp server allocations by ~70% during load of already restored projects #84205
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
Closed
+157
−22
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just to check my understanding, what would happen if we just
return true;in this path?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would restore. The risk is that checking the cache file could mis-report a package as missing (we're parsing a version and id from the path). If we just return true here it could lead to a restore loop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So is the idea that certain project setups, will consistently fail to produce a
project.nuget.cachethat we can use to verify that restore was complete+successful?When does that failure happen? Is it limited to old tooling versions, unusual project setups, ...?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Essentially I am not 100% confident we'll always be able to exactly match packages from the cache file, given that we have to parse the package id and versions from the file path.
I haven't been able to come up with an exact scenario where it breaks, but I can easily imagine how it could break (nuget path changes to not include version, some kind of mismatch in package path and package id, casing differences, encoding differences, etc).
So I left the original code in there as a defensive fallback (which is still better than before due using STJ).
One alternative is to instead hand-roll a parser for the project.assets.json and only use that - I think we could get similar allocations as using the cache file, but we'd no longer be using the nuget API.