git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Karl Stenerud <kstenerud@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: notify alternative to auto gc?
Date: Tue, 29 Jun 2010 08:46:47 +0200	[thread overview]
Message-ID: <vpqtyom72ug.fsf@bauges.imag.fr> (raw)
In-Reply-To: <5D3639C2-2528-4125-91E0-8D78D4844511@gmail.com> (Karl Stenerud's message of "Mon\, 28 Jun 2010 12\:52\:13 -0400")

Karl Stenerud <kstenerud@gmail.com> writes:

> In the case which I observed, the time from typing "git pull" until
> the auto-gc notification was a few seconds.  The time from the
> notification until gc completion, however, was 3-4 minutes.

The missing bit here is how often this happens.

Once you did an actual "git gc", your repository is stored in a single
pack file, and only new files are stored unpacked or in separate
packs. Subsequent "git gc --auto" will just pack unpacked objects
together by groups of approximately "gc.auto" (i.e. 6700), which is
quick, until you reach "gc.packlimit" (i.e. 50). You'll trigger an
expansive repack only after that. So, roughly, you'll get an expansive
repack after creating 300,000 object files (unless you ran "git gc" in
the meantime). Unless you do very nasty things with your repo, that
really means "not often", and especially "not often enough that you
should care" in 99.9% cases.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2010-06-29  6:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 16:10 notify alternative to auto gc? Karl Stenerud
2010-06-28 16:26 ` Ævar Arnfjörð Bjarmason
2010-06-28 16:52   ` Karl Stenerud
2010-06-29  6:46     ` Matthieu Moy [this message]
2010-06-30  2:27   ` Sam Vilain
2010-06-28 16:27 ` Matthieu Moy
2010-06-28 16:29 ` Chris Packham
2010-06-28 16:56   ` Karl Stenerud
2010-06-28 17:07   ` [PATCH/RFC] Documentation/git-gc.txt: add reference to githooks Chris Packham
2010-06-28 18:43     ` Marc Branchaud
2010-06-29 15:43       ` Junio C Hamano
2010-06-29 16:00         ` Chris Packham
2010-06-29 16:26     ` Junio C Hamano
2010-06-29 18:16       ` Chris Packham
2010-06-30 20:41         ` [PATCHv2] " Chris Packham
2010-09-21 18:14     ` [PATCH/RFC] " David Brown
2010-09-21 20:52       ` Allow git remote add but not git clone ( was Re: [PATCH/RFC] Documentation/git-gc.txt: add reference to githooks) Chris Packham
2010-09-21 21:01         ` David Brown
2010-09-21 23:18       ` Re* [PATCH/RFC] Documentation/git-gc.txt: add reference to githooks Junio C Hamano
2010-06-28 18:58   ` notify alternative to auto gc? Eric Raible
2010-06-28 19:02     ` Jacob Helwig

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=vpqtyom72ug.fsf@bauges.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=kstenerud@gmail.com \
    /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).