Comment 2 for bug 405251

> The actual new commits in that pull changes about 40 small files.

The log you attached contradicts this: it appears to show 100 new files, and a further 99 modified files.

The network protocol overhead in that log is very low (<100kB). i.e. the vast bulk of that transfer was revision data. If too much is transferred it would be some sort of bug in the way bzr selects which revisions to transfer.

Can you try doing a "bzr branch" of your local branch to a new, standalone branch (i.e. not in a shared repository, e.g. "bzr branch /home/jal/bzr/vp-trunk /tmp/vp-trunk --no-tree", and compare the size of the files in .bzr/repository/packs in the original and the copy? It may also be interesting to compare the size of that directory in the original before and after "bzr pack".

The cpu use is almost certainly a bug, but it'll probably be easier to diagnose once we figure out why you are seeing much larger transfers than expected.

Oh, can you also check to see if the repository format on the server and the client matches?