regression? branching lp:branch into empty local shared repo is very slow

[John Arbash Meinel]

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

Alexander Belchenko wrote:
> I've tried to get lp:python/2.5 branch. I'm doing:
> 
> bzr init-repo --no-trees python.bzr --1.9-rich-root
> cd python.bzr
> bzr get lp:python/2.5
> 
> After that the last command spending several hours in the phase "Finding
> revisions" with network speed of about 1KB/sec. If I run the same
> command outside the shared repo then it starts fetching revisions almost
> immediately. Something wrong here.
> 
> bzr 2.1.0b4 (standalone installer) @ Windows XP.

With a repository created, it will walk the revision graph to find if
any of the revisions are present locally. Without one, it knows that you
need everything, and sends a single "give me everything" request.

Looking at -Dhpss, I see a whole lot of:
187.259  hpss call w/body: 'Repository.get_parent_map',
'~python-dev/python/2.5/', 'include-missing:',
'svn-v3-trunk1:6015fed2-1504-0410-9fe1-9d1591cc4771:python%2Ftrunk:47100'
('svn-v3-trunk1:6015fe'...)
187.259                97 bytes
187.560     result:   ('ok',)
187.560                108 body bytes read

Which looks like it is getting 1 revision and its parents at a time.
Some of this is because the python branch is just very linear. However,
I thought that 'Repository.get_parent_map' was supposed to expand the
revisions requested. (Always return ~64kB of parent information per
request.)

And that might be the regression.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktIekMACgkQJdeBCYSNAAOW5wCeNba+cuhgQUczICoHmiNx0o7+
CZsAnRaTeco3tlEdlYf0guApLny8XbPY
=mx7s
-----END PGP SIGNATURE-----