Re: 'git gc --aggressive' effectively unusable

The environment is the same as for the reflog problem, but I should have 
added that info anyway. Here it is again.

On Saturday 03 April 2010, Frans Pop wrote:

I have a git-svn checkout of a subversion repo which I wanted to
compress as much as possible. 'git gc --aggressive' starts to run fairly
well, but eats more and more memory and gets slower and slower. After it
gets to about 45% or 50% progress slows down noticeably and so far I
haven't had the patience to let it finish (40 minutes is already way too
long).

I'm seeing this with both git 1.6.6.1 and 1.7.0.3 on the same repo.
Environment:
- Debian amd64/Lenny; Core Duo x86_64 2.6.34-rc3 -> 1.6.6.1
- Debian i386/Sid; chroot on the same machine -> 1.7.0.3