From: Eric Wong <email@example.com> To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org> Cc: Git Mailing List <email@example.com>, Junio C Hamano <firstname.lastname@example.org>, Jeff King <email@example.com>, Vicent Marti <firstname.lastname@example.org> 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) In-Reply-To: <CACBZZX7R5svNJ+Ak3LFh8+kY48i6V7Yo6JDS+PSDJCkZ5vHb6w@mail.gmail.com> Ævar Arnfjörð Bjarmason <email@example.com> wrote: > On Mon, Apr 3, 2017 at 11:34 PM, Eric Wong <firstname.lastname@example.org> wrote: > > Ævar Arnfjörð Bjarmason <email@example.com> 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 > ever-growing. It might be blame/annotate specifically, I was remembering this thread from a decade ago: https://firstname.lastname@example.org/T/ > 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 Æ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
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 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 \ --in-reply-to=20170403223956.GA3537@whir \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH/RFC] gitperformance: add new documentation about git performance tuning' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).