-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
HttpClientMiniStressTest: Disable parallelism #34941
HttpClientMiniStressTest: Disable parallelism #34941
Conversation
Currently, it's possible for 4 different instances of SingleClient_ManyGets_Sync to run in parallel, each using up to 2 x 5000 sockets, totaling in 40,000 sockets. way beyond the original intent of testing 5000 client instances. since this additional stress is random in nature, I believe it is not intentional. This change make sure that those tests will not run in parallel, this avoids some issues I've encountered in some systems.
Tagging subscribers to this area: @dotnet/ncl |
I'm checking if I can use this attribute on the base class, please don't merge yet. |
…te on the base class
Great, it's now a single line change, thanks for the quick feedback! |
Thanks, but I don't think it's necessary. These tests don't run in CI, and are only manually-enabled via an environment variable. They're really only intended for use when doing active development for things like performance to help minimize the chances of concurrency bugs sneaking in. |
Currently, it's possible for 4 different instances of SingleClient_ManyGets_Sync to run in parallel, each using up to 2 x 5000 sockets, totaling in 40,000 sockets. way beyond the original intent of testing 5000 client instances. since this additional stress is random in nature, I believe it is not intentional.
This change prevents those tests from running in parallel, this avoids some issues I've encountered in some systems.