Repo: Improve CI performance to avoid throttling #11204
Labels
repo maintenance
things to do with maintenance of the repo, and not with code/docs
triage
Waiting for team members to take a look
Comments
This was referenced May 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suggestion
According to https://github.com/typescript-eslint/typescript-eslint/actions/metrics/usage, our biggest total minutes in the last month are:
ci.yml(linux): 17,478 minutes across 425 runsci.yml(windows): 7,610 minutes across 207 runssemantic-breaking-change-pr.yml: 613 minutes across 359 runssemantic-pr-titles.yml: 282 minutes across 282 runsa11y-alt-bot.yml: 201 minutes across 201 runs17478 / 245 = >70 minutes of CI time per commit. That's quite a lot! We've started to see more GHA throttling recently. Jobs/runs have been getting stuck waiting to start -> then for GHA runners to free up.
Filing this issue as a general one: what can we do to reduce the throttling in CI?
Additional Info
These more specific issues are split out of or generally related to this one:
markdownlinttoremark-lint#3223: using ESLint for Markdown linting would reduce the number of jobs per commit by onesemantic-pr-titles.ymlanda11y-alt-bot.yml. That should improve a teeny bit for reducing our number of runs per commit / event.💖
The text was updated successfully, but these errors were encountered: