One runner with many jobs *vs* a few runners with a few jobs

Assuming I have a single, beast machine for CI runners and just one CI project. Is there any advantage between

  • start a single runner with 100 jobs limit
  • start 5 runners with 20 jobs limit each

I understand from the docs that a runner can run multiple jobs simultaneously thus this question arose in my head


runners execute tasks in parallel and are designed for the concurrent approach. Therefore it is more convenient to just start and maintain one runner, instead of multiple ones which may require additional maintenance and monitoring overhead.