pushing git repo causes repacking

[Cody Russell]

I'm pushing a rather large git repo, and after it eventually pushed all the revisions it's been in the process of repacking for many hours.

[#############/ ] 11278352KB 120KB/s | repacking texts:texts 102244/125295

[Robert Collins (lifeless)]

So, this is packing over the network - which is slow :)

bzr auto packs after a cross-format push that did data conversion; however this should happen on the server if the conversion streamed.

Its possible bzr-git doesn't support getting a stream, or that it interferes with the use of streaming, meaning that pushes from git to bzr will be using VFS access and thus pack directly (as this has).

Can you look in your bzr log for the 'packing ...' line, which has the repository types, and paste that in here?

[Robert Collins (lifeless)]

On Wed, 2009-11-18 at 07:22 +0000, Jelmer Vernooij wrote:
> ** Project changed: bzr-git => bzr

Why?

Please remember that bugs are a conversation and describe why you are
changing something if there is any chance of confusion.

-Rob

[Nir Soffer (nirs)]

I have the same issue with pushing a tiny branch to another machine on the local lan.

The branch was created from: svn+https://unity.svn.sourceforge.net/svnroot/unity/trunk

The branch uses a large shared repository (1.4G) used for many other projects.

It seems that pushing that tiny unity branch cause repacking of the whole repository - I see "text: 31380/34176.

The repacking took about 20-30 minutes.