mirror of
https://github.com/Unleash/unleash.git
synced 2026-09-10 22:25:45 +00:00
Gastón Fournier
85750e911b
Small backend CI sharding comparison and would like your take on the trade-off. - [Unsharded](https://github.com/bricks-software/unleash-enterprise/actions/runs/30802484505): 8m31s wall-clock / runner time. - [4 backend shards](https://github.com/bricks-software/unleash-enterprise/actions/runs/30832960347): slowest shard finished in 4m06s, so the backend result arrived ~4m25s earlier. - The problem is the four shard jobs consumed 14m41s total runner time. Almost 2× the unsharded run, due to duplicated PostgreSQL startup, checkout, install, lint, and build. The trade-off: roughly halve feedback time when capacity is available, in exchange for 2x compute time. There is also a minor benefit when rerunning failed tests (potentially flaky): you can rerun one shared instead of a full ~8 minute full job.
