Repository navigation
[experiment] ci(backend): 3 xdist workers (control) - #129366
Closed
sentry-junior[bot] wants to merge 1 commit into
Closed
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
Co-Authored-By: Joshua Li <14209781+joshuarli@users.noreply.github.com>
github-actions
Bot
added
the
Scope: Backend
sentry-junior
Bot
added
the
Trigger: Override Selective Testing
Contributor
Author
|
Result: 3 workers is 6.1% slower than 4 (SE about 2%), normalized for runner CPU model. That's the second 3-worker run to show it, so 4 is confirmed. Closing. |
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
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.
Do not merge. A stacked experiment on #129338: it changes only
XDIST_WORKERSfrom 4 to 3.This repeats the 3-worker control. The first control was 7,057s of summed test time against 6,194–6,535s for 4 workers. Runner CPU types change shard times by up to 1.9×, so one run per setting is weak evidence.
via @joshuarli.
--
View Session [Sentry]