push performance..

[Robert Collins]

So one reason push is slow is because of this:

say the remote repo is at revision A

I branched from revision B, did a local change C, then merge from the
remote repo committing that as D.

The revision parents are:
A: [B]
B: []
C: [B]
D: [C, A]

Now I do a push, which we hope would only push the unique content for C,
and D.

What happens though, is that all the files altered by A are listed in
the commit of D as a diff against C. So if this commit A altered many
files, pushing D ends up checking all those files indexes for the
presence of their revisions even though the revision A is presumed to be
fully installed in the remote repository.

I proposed that we filter the fileids which we will check by the
revisions we know to be be fully installed in the remote repository, and
if there are no interesting revisions left for a given fileid, we dont
bother checking it.

-Rob



-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060817/db63fce9/attachment.pgp