…ordLimit from 100000 to 30000 to keep Nightly run time under 60 minutes

…or of 6 instead of a factor of 2 to keep Nightly run time under 60 minutes

…r of 6 instead of a factor of 2 to keep Nightly run time under 60 minutes

… Azure DevOps over the 1 hour time limit allowed

…Reduced amount of pause and run time for concurrency tests to keep the total test time below 1 hour

…ordLimit from 100000 to 30000 to keep Nightly run time under 60 minutes

…ly instances by 50%

…his test runs out of memory on x86

…o stay under the 1 hour job limit in Azure DevOps

…r from 2 to 1.5

…estMockAnalyzer): Reduced maximum nightly iterations by 50%

…tcorapp2.1

…prevent them from timing out Azure DevOps.

…mVectorCorruption() to assist with debugging occasional test failures on Linux/macOS

…gDocuments() Reduced size of big documents to keep test time under 1 hour

…for debugging

…: Increased ramBuffer size to offset the fact that LuceneTestCase.AtLeast() was decreased.

…ts to prevent them from going over Azure's 1hr time limit and detect which test(s) limits are problematic

…t 47-55 minutes in order to allow the test results to be uploaded. This will make troubleshooting which tests are taking too long easier.

…ctory(): increased timeout to 30 minutes

…eleaseRace(): Reduced nightly probability by 50% on x86 to keep from timing out