From: Eric Wong <firstname.lastname@example.org>
To: "Ævar Arnfjörð Bjarmason" <email@example.com>
Cc: Git Mailing List <firstname.lastname@example.org>,
Junio C Hamano <email@example.com>, Jeff King <firstname.lastname@example.org>,
Vicent Marti <email@example.com>
Subject: Re: [PATCH/RFC] gitperformance: add new documentation about git performance tuning
Date: Mon, 3 Apr 2017 22:39:56 +0000 [thread overview]
Message-ID: <20170403223956.GA3537@whir> (raw)
Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> wrote:
> On Mon, Apr 3, 2017 at 11:34 PM, Eric Wong <email@example.com> wrote:
> > Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> wrote:
> >> - Should we be covering good practices for your repo going forward to
> >> maintain good performance? E.g. don't have some huge tree all in
> >> one directory (use subdirs), don't add binary (rather
> >> un-delta-able) content if you can help it etc.
> > Yes, I think so.
> I'll try to write something up.
> > I think avoiding ever growing ChangeLog-type files should also
> > be added to things to avoid.
> How were those bad specifically? They should delta quite well, it's
> expensive to commit large files but no more because they're
It might be blame/annotate specifically, I was remembering this
thread from a decade ago:
> One issue with e.g. storing logs (I keep my IRC logs in git) is that
> if you're constantly committing large (text) files without repack your
> .git grows by a *lot* in a very short amount of time until a very
> expensive repack, so now I split my IRC logs by month.
Yep, that too; as auto GC is triggered by the number of loose
objects, not the size/packability of them.
next prev parent reply other threads:[~2017-04-03 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 21:16 [PATCH/RFC] gitperformance: add new documentation about git performance tuning Ævar Arnfjörð Bjarmason
2017-04-03 21:34 ` Eric Wong
2017-04-03 21:57 ` Ævar Arnfjörð Bjarmason
2017-04-03 22:39 ` Eric Wong [this message]
2017-04-04 21:12 ` Ævar Arnfjörð Bjarmason
2017-04-04 2:19 ` Jeff King
2017-04-04 15:07 ` Jeff Hostetler
2017-04-04 15:18 ` Ævar Arnfjörð Bjarmason
2017-04-04 18:25 ` Jeff Hostetler
2017-04-05 12:56 ` Duy Nguyen
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).