Comment 1 for bug 223814

On Mon, 2008-04-28 at 18:23 +0000, Abdulaziz Ghuloum wrote:
> Public bug reported:
>
> This is bizarre. Every time I commit locally and try to push to the
> server hosting my repository, bzr goes into a networking spree
> trafficking hundreds of megabytes at times (I can see it in Activity
> Monitor in Mac OS X) before I get pissed off and interrupt it. After
> interrupting it and retrying, it always succeeds instantaneously. This
> has been going on for some time now consistently and it started when I
> upgraded bzr to 1.3 and upgraded the branch formats to the pack (on both
> the server and on my development machine).
>
> Any ideas?

Its trying to tune your repository to ensure continued performance.

It will try to do this until you allow it to succeed.

Not doing it will lead to increased latency on operations and continual
gradual degradation.

You can pack it more quickly by sshing in and running 'bzr pack'. You
can also run 'bzr pack URL' to remotely pack it.

This line:
"""
69.787 Auto-packing repository
<bzrlib.repofmt.pack_repo.RepositoryPackCollection object at 0x221f6b0>,
which has 24 pack files, containing 1461 revisions into 12 packs.
"""

Is the key indicator. 24 packs means the minimum pull speed from this
repository will need 200 round trips; for high latency links this will
perform noticeably slowly.

We have a bug open already that bzr needs to be more informative when
doing this repository maintenance.

 status invalid

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.