Ensure CI/CD can scale in the near future
In our latest meeting about Auto DevOps on by default, we figured out that there are technical concerns about the performances in near future for CI/CD on GitLab.com.
With the current scaling speed, and the increasing number of jobs that are created, it seems that the structure of both code and database is starting to reach a warning threshold. This is not related to the infrastructure (that is a different topic), but to the application itself.
We should take actions to ensure we can scale our CI/CD in the next year, supporting the increasing number of jobs. This is also a crucial point to allow us to enable Auto DevOps by default on GitLab.com.
The issue to discuss Optimise the ci_builds table.