-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iterating over projects takes over 30 seconds #97
Comments
If you have many projects, then yes, it will take some time to iterate through all of them. It would be good to have some optimisations for Marge to work on different projects simultaneously (as mentioned in #69). For now, a workaround would be to run multiple instances of Marge, each looking at a subset of your projects. As long as these don't overlap, they won't conflict with each other. |
Thanks @JaimeLennox, i came to same conclusion for the workaround. |
Another way would also be to use the root |
@fooishbar Cross-linking for more info about that in #75 (comment) |
@maikelvl Thanks for the pointer. Ultimately we just went with having a single instance per project (or group of related projects, at least), since mutual starvation was starting to become a problem, e.g. if you have two equally-active projects with 35min CI pipelines, then you could only merge one per project per hour ... |
as marge checks each project it is assigned one by one, and having over 50 projects assigned, the whole cycle (with no jobs found) takes ~2 minutes. how to solve this and make marge process assigned jobs sooner?
marge 0.6.1
The text was updated successfully, but these errors were encountered: