file ancestors

[John A Meinel]

Johan Rydberg wrote:
> John A Meinel <john at arbash-meinel.com> writes:
> 
>>>> Regarding building full branch graphs:
>>>>
>>>> Right now revision_graph reads _every_ revision to get parent
>>>> information.  This is quite expensive, esp with a remote revision
>>>> store.  Maybe this information could be cached in a "revision-graph"
>>>> file in ".bzr" directory.  The format could be simple:
>>> Actually, we already have that information. It is in the table of
>>> contents for the inventory.weave file.
> 
> Yes, I know that.  But on my computer it takes ~15 seconds to generate
> the graph, which I think is a bit too long for a "bzr log FILE" --
> those little operations should be _instant_.  I have not yet tried to
> implement my proposed format, but I'm quite sure it is faster to read
> and parse than an weave file that is over 2MB.

I don't believe that revision_graph() utilizes the information in the
inventory.weave. It still reads the revision texts one by one.

You could probably just try useg get_inventory_weave() and see how much
of a speedup you could get.

It probably takes < 1s to read the inventory weave, so I imagine you
would see quite a speedup.

John
=:->

> 
>>>>    REVISION-ID:PARENT[,PARENT[,...]]
>>>>
>>>> If there is no entry for a revision in the file, it should be treated
>>>> as a ghost revision.  
> 
> ~j

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051122/1708fff6/attachment.pgp