From: Jeff King <peff@peff.net>
To: David Kastrup <dak@gnu.org>
Cc: Duy Nguyen <pclouds@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Bump core.deltaBaseCacheLimit to 96m
Date: Mon, 5 May 2014 16:19:28 -0400 [thread overview]
Message-ID: <20140505201928.GA24266@sigill.intra.peff.net> (raw)
In-Reply-To: <874n14tqty.fsf@fencepost.gnu.org>
On Mon, May 05, 2014 at 01:20:09PM +0200, David Kastrup wrote:
> > Would it make more sense to advise git devs to set this per repo
> > instead? The majority of (open source) repositories out there are
> > small if I'm not mistaken. Of those few big repos, we could have a
> > section listing all the tips and tricks to tune git. This is one of
> > them. Index v4 and sparse checkout are some other. In future, maybe
> > watchman support, split index and untracked cache as well.
>
> Shrug. The last version of the patch was refused because of wanting
> more evidence. I added the evidence.
FWIW, I was the one who asked for the evidence, and this patch looks
pretty straightforward and good. We may also want to revisit the data
structure for the delta cache, but that can come separately. My earlier
tests had not shown improvement with just bumping the cache size, but
these ones obviously do. So I think it's worth bumping the default.
-Peff
prev parent reply other threads:[~2014-05-06 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 17:13 [PATCH] Bump core.deltaBaseCacheLimit to 96m David Kastrup
2014-05-05 10:26 ` Duy Nguyen
2014-05-05 10:27 ` Duy Nguyen
2014-05-05 11:03 ` Matthieu Moy
2014-05-05 11:35 ` Duy Nguyen
2014-05-05 11:20 ` David Kastrup
2014-05-05 20:19 ` Jeff King [this message]
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=20140505201928.GA24266@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=pclouds@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).