Speed up conformance runs with parallelism #720
Merged
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 introduces two new flags to the
connectconformance
runner:max-servers
: the number of concurrent server processes to start. Test cases for all of them will be written to the client's stdin in parallel (thread-safe, but interleaving test cases for various servers). Defaults to 4.parallel
: the number of RPCs to issue in parallel when--mode
isserver
(so this only controls the reference client). In--mode
ofclient
, it's up to the client-under-test to implement parallelism. Defaults to 4 * GOMAXPROC (and GOMAXPROC defaults to the number of CPU cores detected).This speeds up conformance runs on my MBP from about 3 minutes down to less than 15 seconds,.