Prune runners that have been inactive for over 3 months
As part of https://gitlab.com/gitlab-org/gitlab/-/issues/321368#note_689886009 I've identified that from most namespaces containing more than 1000 runners (the limit introduced by the ci_runner_limits
for paid plans), only <1% of the runners have contacted GitLab.com recently. There is for example a project with 250K+ runners and a namespace with 350K+ runners. This causes unnecessary load on the database and makes it unnecessarily harder to estimate the performance of a given query.
We've recently enabled ci_runner_limits
on .com with a temporary exception for infringing namespaces/projects. We've contacted the affected users and will normally remove the exceptions with the release of %14.4. Since some customers have 250K+ runners to unregister, the script we provided them will not be responsive enough to go through the whole list in time, and we might need to work with the customers mentioned in https://gitlab.com/gitlab-com/support/support-ops/customer-ticket-generator/-/issues/25 to prune the runners for them.