Index more projects per time
What does this MR do and why?
For the namespaces with so many projects the delay in indexing was quite considerable. For instance, if a namespace has 2000 projects. Then the last project will be indexed in 20_000s
which is almost after 6 hours. This is also the reason the task processing throughput is quite low. We process the task only for this scope where(perform_at: (..Time.zone.now))
. Since the perform_at
for so many tasks was quite in the future, it could process very few tasks at a time.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.