Re: 'git gc --aggressive' effectively unusable
- From
Michael Witten <mfwitten@gmail.com>
- Date
- Apr 3, 2010, 21:33 UTC
- Message-ID
- <p2gb4087cc51004031433xc57e52bbq733d1d3c5f37f238@mail.gmail.com>
- In-Reply-To
- <201004030005.35737.elendil@planet.nl>
On Fri, Apr 2, 2010 at 16:05, Frans Pop <elendil@planet.nl> wrote:
> I haven't had the patience to let it finish
There's your problem.
$ git help gc | sed -n /--aggressive$/,+3p
--aggressive
Usually git gc runs very quickly while
providing good disk space utilization
and performance. This option will
cause git gc to more aggressively
optimize the repository at the expense
of taking much more time. The effects
of this optimization are persistent, so
this option only needs to be used
occasionally; every few hundred
changesets or so.Last time I used this option (on Linus's Linux repo), I let the algorithm do its thing for a couple of hours. Maybe the efficiency could be vastly improved, but it does finish if you let it.
SIncerely, Michael Witten