From: Bryan Turner <bturner@atlassian.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Jeff King" <peff@peff.net>,
"SZEDER Gábor" <szeder.dev@gmail.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Git Users" <git@vger.kernel.org>,
entwicklung@pengutronix.de
Subject: Re: git slow unless piped to cat
Date: Tue, 27 Aug 2019 14:38:57 -0700 [thread overview]
Message-ID: <CAGyf7-EaumF+oZFUhNtifrCvqBr1DjcFh8rgQMswcpwip3Bx7w@mail.gmail.com> (raw)
In-Reply-To: <20190827213248.kzpszutt46ipboq4@pengutronix.de>
On Tue, Aug 27, 2019 at 2:32 PM Uwe Kleine-König
<u.kleine-koenig@pengutronix.de> wrote:
>
> On Tue, Aug 27, 2019 at 02:59:30PM -0400, Jeff King wrote:
> > On Tue, Aug 27, 2019 at 12:04:27PM +0200, Uwe Kleine-König wrote:
> >
> > to see the loose ones. If there are a lot, try:
> >
> > git pack-refs --prune --all
> >
> > (or just "git gc", which does this).
>
> This is a daily updated mirror that is also incrementally backed up. I
> repack from time to time, but hesitate to do this regularily as each
> time I repack the next backup run is "expensive" and I get many small
> packs. I did this now anyhow.
Just noting that Jeff didn't suggest a repack; he suggested a
pack-refs. This should have little, if any impact on your backup
processing, because all it's going to do is rewrite the "packed-refs"
file and delete loose refs. It doesn't modify any files under objects/
at all.
Bryan
next prev parent reply other threads:[~2019-08-27 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 8:15 git slow unless piped to cat Uwe Kleine-König
2019-08-27 8:41 ` SZEDER Gábor
2019-08-27 8:56 ` Uwe Kleine-König
2019-08-27 9:12 ` Philipp Zabel
2019-08-27 9:44 ` SZEDER Gábor
2019-08-27 10:04 ` Uwe Kleine-König
2019-08-27 10:33 ` SZEDER Gábor
2019-08-27 10:56 ` Uwe Kleine-König
2019-08-27 11:28 ` Michal Suchánek
2019-08-27 18:59 ` Jeff King
2019-08-27 21:32 ` Uwe Kleine-König
2019-08-27 21:38 ` Bryan Turner [this message]
2019-08-28 10:24 ` Uwe Kleine-König
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=CAGyf7-EaumF+oZFUhNtifrCvqBr1DjcFh8rgQMswcpwip3Bx7w@mail.gmail.com \
--to=bturner@atlassian.com \
--cc=entwicklung@pengutronix.de \
--cc=git@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=peff@peff.net \
--cc=szeder.dev@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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.
Code repositories for project(s) associated with this public 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).