Comment 11 for bug 456077
Revision history for this message
| GuilhemBichot (guilhem-bichot) wrote Re: bzr branch: unacceptable slow | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
One more subquestion for 2): as the upgrade takes 48 hours, which is too long downtime, we'll need to design a multi-step upgrade; I guess:
take original repo offline; copy the original repo (minutes); take the original repo online;
upgrade the copy's format (48 hours);
take the original repo offline; pull the original's repos changes into the copy (minutes); take the original repo online; eof.
Something observed by the colleague when on-the-fly conversion happened:
he had:
his laptop (bzr 2.0, 2a repo) branching from our central host (bzr 1.17, 1.9-or-1.14 repo):
- laptop: no bzr cpu use, no disk size increase
- no network traffic
- central host: bzr running at 100% cpu (user), increasing slowly in memory use ~450M
So it looks like the central host (bzr 1.17) knows the 2a format and performs the conversion while the laptop waits for the converted result?