From: Eric Wong <email@example.com>
To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org>
Cc: email@example.com, Junio C Hamano <firstname.lastname@example.org>,
Jeff King <email@example.com>
Subject: Re: [PATCH/RFC] gitperformance: add new documentation about git performance tuning
Date: Mon, 3 Apr 2017 21:34:40 +0000 [thread overview]
Message-ID: <20170403213440.GA1409@whir> (raw)
Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> wrote:
> Add a new manpage that gives an overview of how to tweak git's
> There's currently no good single resource for things a git site
> administrator might want to look into to improve performance for his
> site & his users. This unfinished documentation aims to be the first
> thing someone might want to look at when investigating ways to improve
> git performance.
> Signed-off-by: Ævar Arnfjörð Bjarmason <email@example.com>
> I've been wanting to get something like this started for a while. It's
> obviously woefully incomplete. Pointers about what to include would be
> great & whether including something like this makes sense.
Thanks for doing this. I hope something like this can give
server operators more confidence to host their own git servers.
> Things I have on my TODO list:
> - 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 think avoiding ever growing ChangeLog-type files should also
be added to things to avoid.
> --- /dev/null
> +++ b/Documentation/gitperformance.txt
> @@ -0,0 +1,107 @@
> +Server options to help clients
> +These features can be enabled on git servers, they won't help the
> +performance of the servers themselves,
Is that true for bitmaps? I thought they reduced CPU usage on
the server side...
A sidenote: I wonder if bitmaps should be the default for bare
repos, since bare repos are likely used on servers.
> but will help clients that need
> +to talk to those servers.
> +- config: "repack.writeBitmaps=true" (see
> + linkgit:git-config). Spend more time during repack to produce
> + bitmap index, helps clients with "fetch" & "clone" performance.
next prev parent reply other threads:[~2017-04-03 21:34 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 [this message]
2017-04-03 21:57 ` Ævar Arnfjörð Bjarmason
2017-04-03 22:39 ` Eric Wong
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).