git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: git@vger.kernel.org
Subject: Re: 'git gc --aggressive' effectively unusable
Date: Sat, 3 Apr 2010 15:33:20 -0600	[thread overview]
Message-ID: <p2gb4087cc51004031433xc57e52bbq733d1d3c5f37f238@mail.gmail.com> (raw)
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

  parent reply	other threads:[~2010-04-03 21:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02 22:05 'git gc --aggressive' effectively unusable Frans Pop
2010-04-02 22:12 ` Frans Pop
2010-04-03 21:16 ` Frans Pop
2010-04-03 21:33 ` Michael Witten [this message]
2010-04-03 21:42   ` Michael Witten
2010-04-03 23:23   ` Frans Pop
2010-04-03 23:42     ` Michael Witten
2010-04-04  0:14     ` Miles Bader
2010-04-04 14:50       ` Michael Poole
2010-04-04 20:38         ` Jeff King
2010-04-04 21:49           ` Jeff King
2010-04-05 21:07             ` Nicolas Pitre
2010-04-04  4:27     ` Mike Galbraith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p2gb4087cc51004031433xc57e52bbq733d1d3c5f37f238@mail.gmail.com \
    --to=mfwitten@gmail.com \
    --cc=elendil@planet.nl \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).