<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=12698) </details> <!--IssueSummary end--> _A corrective action of https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/7173_ We observed in https://gitlab.com/gitlab-com/gl-infra/production/issues/937 that when Redis is under a lot of stress, it can take `UpdateAllMirrorsWorker` considerable time (we observed over 100 seconds) to enqueue all `ProjectImportScheduleWorker` which could lead to the piling up of overdue mirrors. Making the [batch size](https://dev.gitlab.org/gitlab/gitlab-ee/blob/ac9db2a4b6002dc74b4dd6fb7bbddb05af1c2c4c/ee/app/workers/update_all_mirrors_worker.rb#L44) configurable could help us mitigate such piling up by enqueuing more jobs as the enqueuing time, we also observed, doesn't change much with the number of we enqueue.