branches command slow
Bug #197597 reported by
Robert Collins
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Breezy |
Triaged
|
Medium
|
Unassigned |
Bug Description
The bzr branches command over bzr+ssh should use a smart server verb
affects bzr
status confirmed
importance high
--
GPG key available at: <http://
tags: | added: performance |
tags: | added: hpssnovfs |
Changed in bzr: | |
importance: | High → Medium |
tags: |
added: hpss-no-vfs removed: hpssnovfs |
tags: | added: branches |
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
Actually, I don't really see why that would require a smart server verb.
The way I imagine it to work, it should work plenty fast over sftp.
What is it that makes it so slow?
The way I imagine it to work is that it basically does:
for entry in $(ls $url); do
if [ ! -d $entry -o "." = $entry -o ".." = $entry ]; then
:
elif [ -d $entry/.bzr/branch ]; then
echo $url/$entry
else
recurse on $url/$entry
done
So unless you have a lot of (and/or deep) unrelated directories in that area, I can't imagine what would make it take so long. Admitttedly, a smart server verb would avoid a lot of round-tripping, but all the -d test are independent so they shouldn't need to suffer that much from round-trip delays.