Some timings using bzr

[James Westby]

On Fri, 2008-07-11 at 10:43 +0200, David Ingamells wrote:
> The repository in question is a shared repos with a number of branches 
> in it. It was made when bzr 0.98 (I think it was) was the latest 
> released version. I used the default setting for bzr init-repo then. 
> Now, as you say, bzr 1.5 has pack-0.92 as the default. Are there any 
> issues I should be aware of in doing a bzr upgrade?
> What is the best way to update the repos? Can I update one branch and 
> leave the remainder alone? Must I do the upgrade at the shared repos level?

Hi,

Upgrade here will act at the repository level, so you must upgrade
all branches that share the same repository. You can obviosly break
up the shared repo if this won't work for you.

There are two important things to ensure. The first is that all
users have a version of bzr that will understand the new format,
i.e. they all have 0.92 or greater. The second is that all users
upgrade their branches to the pack-0.92 format. While the formats
will interoperate, pulling from pack-0.92 into dirstate-tags is
very slow indeed. This is because they store different data, and
so the extra data in the latter format must be regenerated on
the fly, leading to very long pull times.

Thanks,

James