Cache file commit data so it can be loaded synchronously in the tree viewer
Customer has very large repositories and notice they have to wait 2-5 seconds after page load for commit data to populate. They would like the commit data to load instantaneously with the rest of the page and suggest we explore caching that data.
I understand why that's slow in terms of extracting that info from Git, but isn't there some way to make a speed-space trade-off and cache this?
It would be nice to have such a cache supported by Gitlab, and even more awesome if it knew to pre-generate "hot" paths as new pushes come in and inject them into the cache.
@yorickpeterse Thoughts here?