From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Stephen Morton <stephen.c.morton@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git Scaling: What factors most affect Git performance for a large repo?
Date: Fri, 20 Feb 2015 17:16:14 +0000 [thread overview]
Message-ID: <20150220171614.GA5730@vauxhall.crustytoothpaste.net> (raw)
In-Reply-To: <CAH8BJxEWDb0SDHPS_ZnPzz0QEbryw2GCv2RtJm2u_6rPH566hg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
On Fri, Feb 20, 2015 at 11:06:44AM -0500, Stephen Morton wrote:
>2. I'd not heard about bitmap indexes before this thread but it sounds
>like they should help me. In limited searching I can't find much
>useful documentation about them. It is also not clear to me if I have
>to explicitly run "git repack --write-bitmap-indexes" or if git will
>automatically detect when they're needed; first experiments seem to
>indicate that I need to explicitly generate them. I assume that once
>the index is there, git will just use it automatically.
Pack bitmaps are a way of speeding up clones and fetches by precomputing
reachability information. Practically, this means that the initial
"Counting objects" phase is instantaneous for clones and much faster for
fetches.
The way I've done it in the past is to set repack.writeBitmaps = true in
/etc/gitconfig on the server. (I highly recommend enabling reflogs in
the same place.) Then you'll need to ensure that git gc runs
periodically so that bitmaps are generated.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-20 17:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 21:26 Git Scaling: What factors most affect Git performance for a large repo? Stephen Morton
2015-02-19 22:21 ` Stefan Beller
2015-02-19 23:06 ` Stephen Morton
2015-02-19 23:15 ` Stefan Beller
2015-02-19 23:29 ` Ævar Arnfjörð Bjarmason
2015-02-20 0:04 ` Duy Nguyen
2015-02-20 12:09 ` Ævar Arnfjörð Bjarmason
2015-02-20 12:11 ` Ævar Arnfjörð Bjarmason
2015-02-20 14:25 ` Ævar Arnfjörð Bjarmason
2015-02-20 21:04 ` Junio C Hamano
2015-03-02 19:36 ` Ævar Arnfjörð Bjarmason
2015-03-02 20:15 ` Junio C Hamano
2015-02-20 22:02 ` Sebastian Schuberth
2015-02-24 12:44 ` Michael Haggerty
2015-03-02 19:42 ` Ævar Arnfjörð Bjarmason
2015-02-21 3:51 ` Duy Nguyen
2015-02-19 23:38 ` Duy Nguyen
2015-02-20 0:42 ` David Turner
2015-02-20 20:59 ` Junio C Hamano
2015-02-23 20:23 ` David Turner
2015-02-21 4:01 ` Duy Nguyen
2015-02-25 12:02 ` Duy Nguyen
2015-02-20 0:03 ` brian m. carlson
2015-02-20 16:06 ` Stephen Morton
2015-02-20 16:38 ` Matthieu Moy
2015-02-20 17:16 ` brian m. carlson [this message]
2015-02-20 22:08 ` Sebastian Schuberth
2015-02-20 22:58 ` brian m. carlson
-- strict thread matches above, loose matches on Subject: below --
2015-02-20 6:57 Martin Fick
2015-02-20 18:29 ` David Turner
2015-02-20 20:37 ` Martin Fick
2015-02-21 0:41 ` David Turner
2015-02-20 19:27 ` Randall S. Becker
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=20150220171614.GA5730@vauxhall.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=stephen.c.morton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.