Open coury-clark opened 2 years ago
Heads up @joelkw @felixfbecker @vovakulikov @unclejustin - the "team/code-insights" label was applied to this issue.
Hey, @sourcegraph/batchers (@eseliger @LawnGnome @courier-new @adeola-ak @BolajiOlajide @malomarrec @chrispine @danielmarquespt) - we have been mentioned. Let's take a look.
I looked at the two calls a since the firstEverCommit is already cached I was thinking wrapping the findRecentCommit
to first attempt to pull it from the commit_index in postgres and then fall back to calling the gitserver if the index isn't sufficiently up to date could provide a greater decrease in the calls to gitserver.
Notebook with some context: https://sourcegraph.com/notebooks/Tm90ZWJvb2s6NjUy
Reduce the number of gitserver interactions from the Insights background process by batching the requests per repository.