Comment 1 for bug 248604

Is this on a Knit format repository, or a Pack format repository?

The dev branch since about 1.3 has removed the Transaction cache for Knit repositories. We've been continually restoring it for each release (1.4, 1.5).

Out of curiosity, does this mean b.repository.get_revisions(rh) is still fast in dev? (It is sort of implied by your comments)

I don't know whether we plan to restore the transaction cache yet again for the 1.6 release. Knits are sort of fading as Robert brings in more patches to align the internals with pack style repositories.

My personal feeling is that the cache should be kept for Knit repos. I believe Robert wanted it out to help force developers to move apis over to better ones (like using get_revisions() instead of looping over get_revision). Though as most of us are now solely on pack repos, nobody really realizes how much performance on Knit repos has regressed. So that part of the experiment is a bit of a failure.