ci: attempt to shard huge test targets more#98834
ci: attempt to shard huge test targets more#98834craig[bot] merged 1 commit intocockroachdb:masterfrom
Conversation
|
This change is |
7e0de19 to
aa5994c
Compare
|
It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR? 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
0da47f0 to
b311d92
Compare
b311d92 to
f91c8a7
Compare
|
|
||
| test_suite( | ||
| name = "small_tests", | ||
| name = "ccl_tests", |
There was a problem hiding this comment.
Why not maintain the small, medium, large, enormous categories for CCL tests?
There was a problem hiding this comment.
Good question. Because we don't use them, we can easily add them if we need to though.
| ], | ||
| shard_count = 16, | ||
| tags = ["cpu:2"], | ||
| shard_count = 48, |
There was a problem hiding this comment.
A few questions:
- How does shard count interact with
cpu:2(orcpu:1in other cases)? - Why change some to 48 but not others?
There was a problem hiding this comment.
Why change some to 48 but not others?
We upload bazel trace profile to artifacts on each unit tests run. I looked at some runs, found targets that had large shards or bottle-necking the process, and sharded them more. Mainly, logictests, backupccl, schemachangerccl, kvserver. If a logictests package has less than 48 tests, it gets n number of shards where n is the number of tests.
How does shard count interact with cpu:2 (or cpu:1 in other cases)?
Good question. Looking.
There was a problem hiding this comment.
How does shard count interact with cpu:2 (or cpu:1 in other cases)?
Each shard gets n cores if cpu:n is used. I tried to play with it but didn't notice any changes so preferred to keep it unchanged.
c5b816a to
8d35f3d
Compare
pkg/cmd/generate-bazel-extra/main.go
Outdated
| "-flaky", | ||
| "-integration", | ||
| "%[1]s", | ||
| "-ccl_test" |
There was a problem hiding this comment.
Nit: Keep the list alphabetized? (Put -ccl_test after -broken_in_bazel)
|
LGTM for backupccl |
This code change attempts to shard some test targets that could benefit from more sharding. It also splits unit tests in TeamCity into two runs: ccl unit tests, and non-ccl unit tests. The current build config will be used to run non-ccl unit tests. The new build config will be used for ccl tests (those under `pkg/ccl`). This cuts unit tests wall time by half while keeping machine time almost the same. Release note: None Epic: none
0d5f80e to
69921eb
Compare
|
TFTRs! bors r=rickystewart |
|
Build succeeded: |
This code change attempts to shard some test
targets that could benefit from more sharding. It
also splits unit tests in TeamCity into two runs:
ccl unit tests, and non-ccl unit tests. The current
build config will be used to run non-ccl unit tests.
The new build config will be used for ccl tests (those
under
pkg/ccl). This cuts unit tests wall time byhalf while keeping machine time almost the same.
Release note: None
Epic: none