git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@fluxnic.net>
To: Jon Nelson <jnelson@jamponi.net>
Cc: git@vger.kernel.org
Subject: Re: git gc / git repack not removing unused objects?
Date: Sat, 06 Feb 2010 20:16:58 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1002061935180.1681@xanadu.home> (raw)
In-Reply-To: <cccedfc61002060553w464d5d9drd582b3b3c3f35227@mail.gmail.com>

On Sat, 6 Feb 2010, Jon Nelson wrote:

> Last night, the repo size was 153G after removing some commits and
> objects by way of git filter-branch.
> I'm using "du -sh" in the .git directory to determine the disk usage.
> 
> Before: 136G
> git repack -dAl
> After: 153G

Why are you using -A instead of -a ?

> Then, just to make sure of some things, I changed nothing and simply
> re-ran "git repack -dAl".
> After: 167G

Could you run 'git count-objects -v' before and after a repack in such 
cases as well?

> [pack]
>         packsizelimit = 256m

Why are you using this?

> pack.packsizelimit=2M

This is even worse.  150G / 2M per pack = approx 75000 packs.

What you should be aiming for is a _single_ pack for best performances.  
A couple packs is common and doesn't make much of a difference.  A 
hundred packs is getting a bit large.  But 75000 packs is totally 
insane.


Nicolas

  reply	other threads:[~2010-02-07  1:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 19:45 git gc / git repack not removing unused objects? Jon Nelson
2010-02-05 20:51 ` Nicolas Pitre
2010-02-05 21:04   ` Jon Nelson
2010-02-05 21:45     ` Nicolas Pitre
2010-02-06 13:53       ` Jon Nelson
2010-02-07  1:16         ` Nicolas Pitre [this message]
2010-02-07 17:48           ` Jon Nelson
2010-02-07 23:40             ` Jon Nelson
2010-02-08  2:11               ` Nicolas Pitre
2010-02-08 17:12                 ` Jon Nelson

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=alpine.LFD.2.00.1002061935180.1681@xanadu.home \
    --to=nico@fluxnic.net \
    --cc=git@vger.kernel.org \
    --cc=jnelson@jamponi.net \
    /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).