perf: check manifests concurrently in scan.Dir - #29
Merged
Conversation
Each manifest's Check is a separate network round-trip to its resolver, so run them in their own goroutine instead of sequentially — a project with several manifest kinds would otherwise serialize their resolver timeouts (10s each) into a slow SessionStart hook.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
scan.Dirchecked each manifest's dependencies sequentially, and eachCheckis a network round-trip to that ecosystem's resolver. A project with several manifest kinds serialized their resolver timeouts (up to 10s each) into a slowerSessionStarthook.Changes
Checkin its own goroutine, guarded by a mutex when appending tofindings, thenwg.Wait()before sorting.