bzr log: quadratic(?) performance against large SVN repository

[Tres Seaver]

Trying to run 'bzr log' in the following checkout was unusably slow (I killed it after
20 minutes):

 $ bzr info .
 Lightweight checkout (format: subversion-wc)
 Location:
   light checkout root: .
    checkout of branch: http://svn.python.org/projects/peps/trunk
     shared repository: .
 $ bzr log pep-0345.txt
 ....
 ^C

It appeared to be re-fetching information for the 70000+ revisions in the repository
over and over and over and over....

[Tres Seaver (tseaver)]

Superficially similar to:

 https://bugs.launchpad.net/bzr-svn/+bug/110175

which has been closed for two years now.

Perhaps related to:

 https://bugs.launchpad.net/bzr-svn/+bug/191731

[Jelmer Vernooij (jelmer)]

Which versions of bzr/bzr-svn are you using?

[Tres Seaver (tseaver)]

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

Jelmer Vernooij wrote:
> Which versions of bzr/bzr-svn are you using?

 $ dpkg-query --show bzr bzr-svn
 bzr 1.13-2~bazaar1~hardy1
 bzr-svn 0.5.3-1~bazaar1~hardy1

Tres..
- --
===================================================================
Tres Seaver [phone] <email address hidden>
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ+bMG+gerLs4ltQ4RAoT/AJ0V4VPgUJyTPR1gVSotT2X7obXStwCgmx32
Dd7yLthqEaqJfDWTT+xce+Y=
=Px0C
-----END PGP SIGNATURE-----

[Jelmer Vernooij (jelmer)]

Just reproduced this. It looks like this particular code path triggers some inefficiencies in the file id generation code. ("bzr log" without arguments should be quick)

For now, you may be better of creating a bzr branch of the repository and using "bzr log" in that rather than working in a svn working copy. This is relatively fast, here at least:

$ bzr branch http://svn.python.org/projects/peps/trunk peps.bzr
$ cd peps.bzr
$ bzr log pep-0345.txt

[Tres Seaver (tseaver)]

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

Jelmer Vernooij wrote:
> Just reproduced this. It looks like this particular code path triggers
> some inefficiencies in the file id generation code. ("bzr log" without
> arguments should be quick)
>
> For now, you may be better of creating a bzr branch of the repository
> and using "bzr log" in that rather than working in a svn working copy.
> This is relatively fast, here at least:
>
> $ bzr branch http://svn.python.org/projects/peps/trunk peps.bzr
> $ cd peps.bzr
> $ bzr log pep-0345.txt

Thanks for the workaround. Using 'svn log' is another alternative, of
course.

Tres.
- --
===================================================================
Tres Seaver [phone] <email address hidden>
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ+cAc+gerLs4ltQ4RAvW3AJ9JIRi71o75LypQOxhFpmXjBXj6mgCfXTbd
gJPTQi9AgP83cVV7uLZu6ZU=
=9NQu
-----END PGP SIGNATURE-----

[Tres Seaver (tseaver)]

I believe this should now be 'Fix Committed': at least, I'm not seeing quadratic time (or swap death) when pulling revisions from a large SVN repository.