Fetching changelog in monorepos: hundreds of requests for the same data resulting in timeouts. Can it be memoized/cached? #21802
dylang
started this conversation in
Suggest an Idea
Replies: 2 comments 5 replies
-
if the underlying http request is the same, then it's already cached per repo in memory. we've also some caching for github graphql post request. so only the log lines are duplicated per repo |
Beta Was this translation helpful? Give feedback.
2 replies
-
The concurrency limits on github are undesirable. I assume they were added due to some other problem, but otherwise this will really slow down Renovate and contribute to timeouts. Better to address the root cause of those than live with a permanently crippled fetching of one at a time |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Type of discussion.
I'm proposing an idea
Tell us more.
Env:
Github Enterprise. Self hosted. latest build of Renovate.
What's going on:
Details about the log:
Our timeouts and limits are generous, for example:
Here's a snippet of the log:
My guess is getChangeLogJSON should be cached or memoized, but I could be wrong.
Discussion: Can we cache or memoize this, or is something else causing this problem?
Beta Was this translation helpful? Give feedback.
All reactions