Bazaar NG performance on large repositories

[Johan Rydberg]

John Arbash Meinel <john at arbash-meinel.com> writes:

>> Is that something that is hard to change? Would it not be possible to
>> have a file somewhere (in .bzr) for each file under version control that
>> lists the revisions that modified it? These files could be calculated
>> once after an initial pull and then updated on each commit. Then a log
>> for a single command would be very fast. The files could be updated the
>> first time a log on a single file is done or always after pulling (but
>> this would increase the pull time of course).
>
> As I commented, most of this is already done. We don't record deletes in
> that index, and we really should.

What is the plan for "bzr log DIR"?  

One possible solution would be to iterate through the children of the
directory and collect all their revisions.

Another solution would be to record modifications in the
directory-knit.

~j

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20061106/0f32cc28/attachment.pgp