'bzr update' probes the master branch >=3 times
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Breezy |
Triaged
|
Medium
|
Unassigned |
Bug Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The current bzr update code probes for the master branch several times
(which includes probing for the repository format, etc.)
The locations are:
cmd_update.run()
Here it opens the master branch to check if the last_revision is the
same as local, and thus 'nothing to do'.
If they differ, it then calls WT.update() passing in possible
transports (so we won't reconnect, but be *will* re-probe for the
master branch.)
WT.update()
uses a "if self.branch.
requires probing to grab the remote branch, and then throwing it away
right away.
We might consider switching to self.branch.
which doesn't have to actually open the master branch.
Branch.update()
Opens the master branch and finally does something useful with it
(pull)
affects /products/bzr
importance medium
status triaged
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFH29ZsJde
na5lq2FF400dqUs
=j2Fz
-----END PGP SIGNATURE-----
Changed in bzr: | |
status: | Triaged → Confirmed |
tags: | added: performance update |
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Medium |