use history cache when getting last revision of a file #3861
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When browsing FreeBSD project (
main
branch from https://github.com/freebsd/freebsd-src) on internal OpenGrok instance, I noticed that getting xrefs takes way too long - usually bunch of seconds. When looking at what the web app is doing, I noticed CPU load spikes andjstack
revealed that the web app actually retrieved the revision string by getting the history via repository specific code:Given that the FreeBSD Git repository is on the heavier side, this action takes a bit of time.
Looking at the code of
PageConfig#getLastRevFromHistory()
andHistoryGuru#getLastHistoryEntry()
I realized that history cache is avoided. This change fixes that.