From: Junio C Hamano <gitster@pobox•com>
To: Drew Northup <drew.northup@maine•edu>
Cc: Peter Harris <git@peter•is-a-geek.org>,
geoffrey.russell@gmail•com, git@vger•kernel.org
Subject: Re: gc getting called on each git command ... what's wrong?
Date: Wed, 08 Jun 2011 09:50:23 -0700 [thread overview]
Message-ID: <7vhb802row.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1307548930.19438.30.camel@drew-northup.unet.maine.edu> (Drew Northup's message of "Wed, 08 Jun 2011 12:02:10 -0400")
Drew Northup <drew.northup@maine•edu> writes:
>> That's why. See gc.autopacklimit in "git help config" -- by default,
>> git will gc if there are more than 50 pack files.
>
> Do we want to consider ignoring (or automatically doubling, or something
> like that) gc.autopacklimit if that number of packs meet or exceed
> gc.packSizeLimit? I have no idea what the patch for this might look
> like, but it seems to make more sense than this situation.
This is unrelated to the auto-gc, but it also would be fruitful to
question if it is a sane setting to limit packfiles to 30M, when the
repository needs 100 of them (total around 3G??). Just like having too
many loose object files degrade performance (and that is one of the
reasons we pack them in the first place), having many packs will degrade
performance unnecessarily and to a worse degree, as "check which pack has
this particular object" code has to examine all packs, unlike the loose
object case where we let the .git/objects/?? fan-out to give us some
hashing and the filesystem to do the heavylifting for us.
next prev parent reply other threads:[~2011-06-08 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 1:33 gc getting called on each git command ... what's wrong? Geoff Russell
2011-06-08 1:48 ` Peter Harris
2011-06-08 16:02 ` Drew Northup
2011-06-08 16:29 ` Brandon Casey
2011-06-08 16:50 ` Junio C Hamano [this message]
2011-06-08 17:09 ` Jakub Narebski
2011-06-15 1:28 ` Geoff Russell
[not found] ` <BANLkTi=w10KQ3MSd5YuYR+S=eMgywNTY-A@mail.gmail.com>
2011-06-15 15:35 ` Jakub Narebski
2011-06-16 1:46 ` Geoff Russell
2011-06-16 14:14 ` Jakub Narebski
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=7vhb802row.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=drew.northup@maine$(echo .)edu \
--cc=geoffrey.russell@gmail$(echo .)com \
--cc=git@peter$(echo .)is-a-geek.org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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