Comment 1 for bug 672016

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 672016] [NEW] 'bzr branches' is pathologically slow with an svn+ssh URL

  affects bzr-svn
  status triaged
  importance medium

  affects bzr
  status triaged
  medium

On Sun, 2010-11-07 at 02:03 +0000, Glyph Lefkowitz wrote:
> $ time svn ls svn+ssh://svn.twistedmatrix.com/svn/Twisted/branches > /dev/null
>
> real 0m1.724s
> user 0m0.014s
> sys 0m0.015s
>
> $ time bzr branches svn+ssh://svn.twistedmatrix.com/svn/Twisted/branches
> > /dev/null
>
> ...
>
> Actually I got tired of waiting after about three hours and just filed
> the bug.
>
> It did lots of work in the meanwhile, though.
This is caused by the way in which BzrDir.find_branches(transport)
works. It finds all possible control directories first and then filters
out the ones that have a branch attached to them.

In svn, where every directory is a possible control directory, this
doesn't work.

bzr-svn already has a list of branches readily available for each
repository, so it should be able to answer this question without a scan
for branches.

So it would be nice if bzr-svn could provide bzr with the list of
branches under a particular location. I'm not sure what the best way to
do that (in terms of API) is though.

Cheers,

Jelmer