Repository navigation
Speeding up / splitting up self-hosted run for large monorepo #38992
Replies: 3 comments 2 replies
|
I empathise here - I've been in a similar boat! As a few quick questions back to you:
DEBUG: Repository timing splits (milliseconds)
{
"splits": {
"init": 3234,
"extract": 326,
"lookup": 8635,
"onboarding": 1,
"update": 828
}
"total": 13603
}I've got a couple of posts that may be worth a read (relatedly, not an exact fix!)
Yep, and also means that i.e. the Dependency Dashboard would be in an awkward state |
|
Note that #38609 would provide better instrumentation to allow you to investigate exactly how much time different things are taking - you may be able to determine some of this through debug logs, too #38614 was a recent suggestion (which didn't get merged due to the additional complexity) |
|
You can try This way yoou can split the schedule for deps, say 50 deps in each cycle which seems like an hour in your case. Also, setting the This should help you clear the 779 deps in 1-2 days and also will keep the runs short. |
Uh oh!
There was an error while loading. Please reload this page.
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitHub, version 41.163.2
Please tell us more about your question or problem
We're self-hosting renovate, and we need to process a large monorepo (15k deps across 779 dependency files, 20 managers involved). We've already split the renovate run into one for this repo, and one that processes all other repos, which aren't a problem. We're using a GitHub app and request an installation token for this app and pass this to renovate before the run - but this token is limited to an expiry of one hour, which we can't change. This repo takes significantly longer to process, so we can't get a full run in before the token expires.
Are there any ways we can speed this up (e.g. running more in parallel), or split up the run for one repo even further? I've tried:
RENOVATE_TOKENon the fly, but I've seen in a separate discussion that this isn't supportedWhat else can we do here?
Logs (if relevant)
No response
All reactions