Slow log

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Micah Elliott wrote:
> On 2007-12-18 John Arbash Meinel wrote:
> 
>> Micah Elliott wrote:
>>> Why is a simple command like log taking so long?
> 
>> Known bug:
>> https://bugs.launchpad.net/bzr/+bug/172975
>>
>> You can use the associated branch which should make 'bzr log'
>> reasonably faster. (For my machine it was 2-5x faster.)
> 
> Okay, that was easy.  Thanks.  Cut log time down from 12s to 6s.
> 
> But still, log is something that would be nice to have return
> instantaneously for a case like this.  Is there a possibility to
> make it so?  My use case is common, right?
> 

Yes, and it is one of the things being worked on.

The biggest problem at the moment is how we number revisions. The numbering
scheme is only defined (so far) when you see the full ancestry graph, which
means loading the full graph, which is slow.

There are a few possibilities (caching the numbering is one of them). I don't
think I've seen an obvious solution yet. If someone could come up with an
alternate numbering scheme, that would also be possible.

I've been getting my head deep in our Graph code, since that is where we can do
the best work at making things scale to O(changes) rather than O(history).

I have a few patches to land for 1.1 which improve things, or give correct apis
that can start to be used.

I certainly agree. I run "bzr log" all the time, and the recent change was...
unfortunate.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHaFA0JdeBCYSNAAMRAtBwAJ91SzC5Yexpnpz4Qs3PcH8HN6eaHACgyrz9
xmz/v4pISATHvaAvwbVcKoc=
=I24z
-----END PGP SIGNATURE-----