RevList seems to be a common thread in taking a long time
Blame as well on smaller repos
We are surprised that ElasticSearch repo took as long as it did. It shouldn't need to traverse so many commits
Do we cache the blame results to save double lookups later?
Understanding how many revisions are visited between two commits. e.g. the ElasticSearch repo examples have git log showing a few commits between, but when we follow the parents on GitHub we get a lot more commits. Is RevList doing more work than it needs to?
Profiling report: https://docs.google.com/document/d/1Xx6V0PIO_ABVQtrLAg6zY8MpJ-3dvu3yvcTBOpccSw0/edit#