-
Notifications
You must be signed in to change notification settings - Fork 880
Search a project's priority documents first in Navigate To #20615
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
Open
xperiandri
wants to merge
11
commits into
dotnet:main
Choose a base branch
from
xperiandri:fix/navigate-to-priority-documents
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
d2d9115
Build multi-project and multi-target Roslyn solutions in FSharp.Edito…
xperiandri f6afb6e
Search each file of a multi-targeted project once in NavigateTo and r…
xperiandri 46557fb
Test NavigateTo across the target-framework instances of a project
xperiandri f088fcc
Add the release note for the NavigateTo multi-target fix
xperiandri 6763038
Share the parse instead of skipping the file
xperiandri 039df11
Name the navigable items cache's key and entry
xperiandri ac1b3c8
Format the multi-target NavigateTo tests
xperiandri 6236f19
Build the synthetic projects' id list through Seq and materialize once
xperiandri f56537e
Search a project's priority documents first in Navigate To
xperiandri 6e78b9d
Key a kept parse by everything it depends on
xperiandri 810adcd
Note the priority documents instead of the multi-target fix twice
xperiandri 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
Some comments aren't visible on the classic Files Changed page.
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
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
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.
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.
🤖 🕵️ [P2] Priority batching delays all Navigate To results — two 700 ms document loads on 16 workers took about 1.4 s instead of 0.8 s; this API publishes nothing until both batches finish.
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 one I do not think holds, because of which method it is on.
IFSharpNavigateToSearchService.SearchProjectAsyncreturnsTask<ImmutableArray<FSharpNavigateToSearchResult>>: it has no callback and cannot publish anything before it returns, so the user sees nothing from this project until the whole project is searched, with or without the priority split. Ordering the documents inside it cannot delay that — the same documents are searched on the same throttle, only in a different order — and the measured 1.4 s against 0.8 s is what two batches of one document each cost when the batches are run one after another, which is the shape the repro builds rather than the shape here: priority documents and the rest go through onewhenAllThrottledover one sequence, not two awaited halves.Where publishing early does exist is the loading path,
SearchCachedDocumentsAsync, which takesonResultsFoundand reports per document as each finishes — and that one already searches priority documents first, for exactly the reason you are pointing at.If the ordering inside a single throttled pass is measurably worse than none, I would like to see it as a run of the editor tests rather than a synthetic two-document case, since the whole point of the parameter is that Roslyn hands us the documents the user is looking at.