perf(tests): Run unit suite in parallel with pytest-xdist#1425
Merged
Conversation
`make test` ran the 4232-test unit suite serially on a single core despite pytest-xdist already being a dependency. Adding `-n auto` parallelizes collection across all cores, cutting the run from ~95s to ~50s (~2x) with coverage preserved and all tests green.
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
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.
Summary
make testran the 4232-test unit suite serially on a single core, despitepytest-xdistalready being a project dependency. Adding-n autoparallelizes the run across all available cores.Impact
-n autoadapts to the machine — fewer workers on smaller CI runners.Notes
Deeper levers were investigated and rejected as not worthwhile: lazy imports (~7% of per-worker startup) and trimming the autouse fixtures (<1s wall under
-n auto).--dist workstealis ~20% faster still, but exposed a rare flaky failure (a latent test-isolation bug) and is deferred until that is root-caused.