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

Set discovery batch size to 1000 #3896

Merged
merged 3 commits into from
Aug 2, 2022

Conversation

nohwnd
Copy link
Member

@nohwnd nohwnd commented Jul 25, 2022

Description

Measures show that 1000 for discovery size makes it run faster because there is less contention when reporting the test results in parallel. This is because we report through a single channel and so there are less times threads run into each other and need to wait to send back their results.

We also don't want to push the results into a queue because then we have no backpressure.

There no risk that this value will break stuff, if we fail discovering tests we throw the whole dll results away anyway, no matter if we missed 1 tests or 1000 tests from the results.

@@ -38,3 +38,5 @@ static Microsoft.VisualStudio.TestPlatform.Utilities.MSTestSettingsUtilities.Imp
static Microsoft.VisualStudio.TestPlatform.Utilities.MSTestSettingsUtilities.IsLegacyTestSettingsFile(string? settingsFile) -> bool
static Microsoft.VisualStudio.TestPlatform.Utilities.ParallelRunSettingsUtilities.UpdateRunSettingsWithParallelSettingIfNotConfigured(System.Xml.XPath.XPathNavigator! navigator) -> void
static Microsoft.VisualStudio.TestPlatform.Utilities.StringExtensions.Tokenize(this string? input, char separator, char escape) -> System.Collections.Generic.IEnumerable<string!>!
static Microsoft.VisualStudio.TestPlatform.Utilities.InferRunSettingsHelper.UpdateBatchSize(System.Xml.XmlDocument! runSettingsDocument, long batchSizeValue) -> void
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious: Shouldn't the contents of this file be sorted to ensure fewer merge conflicts?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does that ensure less merge conflicts?

@Evangelink Evangelink enabled auto-merge (squash) August 1, 2022 19:50
@nohwnd nohwnd disabled auto-merge August 2, 2022 13:13
@nohwnd nohwnd merged commit 7ce631f into microsoft:main Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants