Optimisations #12
Open
Optimisations #12
Conversation
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
…nally prevent long service startup times for very large repos
…ommits in large repos with long histories across lots of branches
|
Thank you for your pull request! |
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.
This integration has been updated to better handle large repositories, after experiencing slow performance and excessive memory usage while scanning a repository with a long commit history and 100s of branches.
As part of testing these changes the integration was run against the Linux kernel's repository on GitHub. During that process it was undesirable to repeatedly re-clone it over a slow internet connection, so the AlwaysCloneOnStartup config setting has been added on a per-repository basis. I thought the best default value would be false, which changes the current default - hope that's OK.
A side-effect of running integration tests against the Linux repo is it unexpectedly matched some backlog IDs (e.g. B-xxxxx) in your v1sdktesting instance, so some of Linus's commits will be there now and you might want to reset that environment.
Cheers
Ed