Comment 19 for bug 407834

It seems this is the same problem that I am having.

$ bzr info .
Shared repository with trees (format: 2a)
$ bzr info /home/knielsen/devel/repo/mariadb-5.1
Repository branch (format: 1.14 or 1.9)
$ time bzr branch --no-tree /home/knielsen/devel/repo/mariadb-5.1

(/home/knielsen/devel/repo/mariadb-5.1 is a local branch of lp:maria, which
shares most of the history with mysql-6.0)

This has now run for > 24 hours with the CPU pegged at 100%. Process uses
2Gbyte of resident memory.

Note that both of these branches are _local_. So this problem appears to be
distinct from bug 385826.

The machine it is running on is a Core 2 Duo 2.4GHz with 4 Gb RAM and an Intel
SSD disk.

This does appear to be excessive resource consumption even for a conversion
operation. I was trying to follow procedures found here:

    http://doc.bazaar-vcs.org/latest/en/upgrade-guide/index.html#migrating-branches-on-launchpad

(I also tried bzr upgrade, but that died after running for 21 hours, so seems
to have similar performance issues. The failure seems not related to bzr).

If the branch command eventually finishes, I will test if branching between
two repositories both of format 2a also suffers from this problem.

[Does bzr regression tests include testing on the mysql repositories? If not it
might be an idea, as they often seem to provoke various issues.]