[Bug 4595] New: Creating a bundle can be significantly slower depending on parameters, even if the resulting bundle is identical

[mercurial-bugs at selenic.com]

http://bz.selenic.com/show_bug.cgi?id=4595

          Priority: normal
            Bug ID: 4595
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Creating a bundle can be significantly slower
                    depending on parameters, even if the resulting bundle
                    is identical
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: mh+hg at glandium.org
          Hardware: PC
            Status: UNCONFIRMED
           Version: 3.3
         Component: Mercurial
           Product: Mercurial

Background: I stumbled upon it because git-cinnabar (my tool to clone/pull from
mercurial with git) does request all heads including closed ones, which
mercurial doesn't do, and that makes cloning slower than it should. It is
however easy to reproduce with hg bundle:

$ hg clone -U http://hg.mozilla.org/mozilla-central
$ cd mozilla-central
$ time hg bundle --all ../foo.hg
238567 changesets found

real    9m28.227s
user    9m22.944s
sys     0m5.268s

$ time hg bundle --all $(hg heads --close --template '-r {node} ') ../foo2.hg   
238567 changesets found

real    30m45.752s
user    30m40.012s
sys     0m5.708s

$ sha1sum ../foo*.hg
a5a6907e24e39b5bc3182c114c8342d8aec147ce  ../foo.hg
a5a6907e24e39b5bc3182c114c8342d8aec147ce  ../foo2.hg

Both bundles are *exactly* the same, but one took 3 times the time it took to
create the other, just because it was created with explicit revisions for all
the heads (closed or not).

-- 
You are receiving this mail because:
You are on the CC list for the bug.