On 7/1/06, Tels <nospam-abuse(a)bloodgate.com> wrote:
Cache the blame map. In addition, cache it for each
revision. Limit the
cache to "N maps or M megabytes, whatever is reached earlier".
I think it should be possible to generate the blame-map for revision N+1
from the map of revision N and the diff between the revisions.
Locality is poor, any time you talk about caching revisions you're
fighting a losing battle.
We'd really need incremental production of blame maps... Where you can
take a finished blame map for revisions 1..5 and add revisions 6 and 7
and get the 1..7 blame map. Then blame maps could be could simply be
generated and stored.. and when they are requested it would only
require fetching the map and updating it.