Slow CI job investigationSlow CI job investigation
You
Which CI job is slowest and how do we speed it up?
Assistant
The slowest CI job is e2e:web, averaging 14m 20s.
- 62% of its time is Playwright browser install, repeated on every shard.
- Caching
~/.cache/ms-playwrightby lockfile hash should save ~5 minutes per run.
I opened PR #751 with the cache step.
You
Show me where the time goes.
Assistant
Breakdown of the 14m 20s:
| Phase | Time |
|---|---|
| Browser install | 8m 53s |
| Build | 2m 10s |
| Tests | 3m 17s |
You
What does a run look like with the cache warm?
Assistant
After the cache, a warm run takes 9m 05s. Cold runs, such as a lockfile change, stay at about 14 minutes.
You
Would more shards help?
Assistant
Sharding from 4 to 6 would cut test time to about 2m but add roughly $40 a month in runner cost. Not worth it until the cache lands.