git performance suffers for large repositories

bzr-git's push support isn't really yet on par with its fetch support, which works reasonable well for large repositories that have the size of mysql or the kernel.

This is partly due to a lack of support for generating proper git pack files in dulwich (bug 562673) and partly due to the difference in the file formats of bzr and git. Some sort of cache (not fulltext, but git sha -> bzr object identifier) might help iterating over git objects based on a bzr repository more quickly.

This makes it practically impossible to have a viable/updateable fast-export git repository of mysql as bzr fastexport does not seem to properly hand all revisions.

For what it's worth, I also tested the branch proposed in bug 562673 and it does not seem to yield any perceptible improvement.

s/updateable fast-export/updateable/

It is still running after 80 hours and the "pushing revisions" phase has decided to start using 25GB of memory.

The branch for bug 562673 only contains some refactoring that is necessary for the fix, it doesn't actually contain the fix itself yet.

bzr-git's push support isn't really ready for large scale pushes yet because of bug 562673. It's mainly useful for contributing back to upstream branches that are in git (incremental pushes work fine).

What issue are you hitting with bzr-fastexport?

There is a error (I guess in git-fastimport) about not being able to update ref/master (or something) due to a missing commit. But I don't want to keep the "marks" files around and I also want to make repeatable/stable conversions, which (it seems) bzr-fastexport is not capable of.

> It's mainly useful for contributing back to upstream branches that are in git (incremental pushes work fine).

I'm attempting to accomplish something similar, have a downstream branch in git where people can pull/merge from the upstream in bzr.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/23/2011 10:23 PM, Davi Arnaut wrote:
>> It's mainly useful for contributing back to upstream branches
>> that are
> in git (incremental pushes work fine).
>
> I'm attempting to accomplish something similar, have a downstream
> branch in git where people can pull/merge from the upstream in
> bzr.
>

You could try doing the push incrementally, rather than the whole
history from the beginning. Depending on how bzr-git handles
incremental updates, you could push say 1000 revisions at a time.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5VHIsACgkQJdeBCYSNAAMdxgCgir7LZPXDpbAvJnzhhtRCEb2V
D/wAoLPDXCYSkQrsY4e5nWgIWwECO0C7
=6vDk
-----END PGP SIGNATURE-----

A significant part of the slowness (but not the space-inefficiency) is that blobs only enter the idmap when there's a content_changed event. If an InventoryFile shows up with a new revision but without new content, it can cause the file to be rehashed in every subsequent commit until the content actually changes.

Hacking the fallback in _tree_to_objects to forcibly cache any misses makes things several times faster on long complex histories.