From: Matt Graham <mdg149@gmail.com>
To: Joshua Redstone <joshua.redstone@fb.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git performance results on a large repository
Date: Fri, 3 Feb 2012 23:05:40 +0000 [thread overview]
Message-ID: <CALts4TT49VAWPZ6XO9qahDTu=2E425QcRvXx5-75Jv8n4yp8RA@mail.gmail.com> (raw)
In-Reply-To: <CB5179E9.3B751%joshua.redstone@fb.com>
Hi Josh,
On Fri, Feb 3, 2012 at 17:00, Joshua Redstone <joshua.redstone@fb.com> wrote:
> Thanks for the comments. I've included a bunch more info on the test repo
> below. It is based on a growth model of two of our current repositories
> (I.e., it's not a perforce import). We already have some of the easily
> separable projects in separate repositories, like HPHP. If we could
> split our largest repos into multiple ones, that would help the scaling
> issue. However, the code in those repos is rather interdependent and we
> believe it'd hurt more than help to split it up, at least for the
> medium-term future. We derive a fair amount of benefit from the code
> sharing and keeping things together in a single repo, so it's not clear
> when it'd make sense to get more aggressive splitting things up.
>
> Some more information on the test repository: The working directory is
> 9.5 GB, the median file size is 2 KB. The average depth of a directory
> (counting the number of '/'s) is 3.6 levels and the average depth of a
> file is 4.6. More detailed histograms of the repository composition is
> below:
Do you have a histogram of the types of files in the repo?
And as suggested earlier, is svn working for you now because it allows
sparse checkout? I imagine the stats for svn on the full repo would
be comparable or worse to what you measured with git?
next prev parent reply other threads:[~2012-02-03 23:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 14:20 Git performance results on a large repository Joshua Redstone
2012-02-03 14:56 ` Ævar Arnfjörð Bjarmason
2012-02-03 17:00 ` Joshua Redstone
2012-02-03 22:40 ` Sam Vilain
2012-02-03 22:57 ` Sam Vilain
2012-02-07 1:19 ` Nguyen Thai Ngoc Duy
2012-02-03 23:05 ` Matt Graham [this message]
2012-02-04 1:25 ` Evgeny Sazhin
2012-02-03 23:35 ` Chris Lee
2012-02-04 0:01 ` Zeki Mokhtarzada
2012-02-04 5:07 ` Joey Hess
2012-02-04 6:53 ` Nguyen Thai Ngoc Duy
2012-02-04 18:05 ` Joshua Redstone
2012-02-05 3:47 ` Nguyen Thai Ngoc Duy
2012-02-06 15:40 ` Joey Hess
2012-02-07 13:43 ` Nguyen Thai Ngoc Duy
2012-02-09 21:06 ` Joshua Redstone
2012-02-10 7:12 ` Nguyen Thai Ngoc Duy
2012-02-10 9:39 ` Christian Couder
2012-02-10 12:24 ` Nguyen Thai Ngoc Duy
2012-02-06 7:10 ` David Mohs
2012-02-06 16:23 ` Matt Graham
2012-02-06 20:50 ` Joshua Redstone
2012-02-06 21:07 ` Greg Troxel
2012-02-07 1:28 ` david
2012-02-06 21:17 ` Sam Vilain
2012-02-04 20:05 ` Joshua Redstone
2012-02-05 15:01 ` Tomas Carnecky
2012-02-05 15:17 ` Nguyen Thai Ngoc Duy
2012-02-04 8:57 ` slinky
2012-02-04 21:42 ` Greg Troxel
2012-02-05 4:30 ` david
2012-02-05 11:24 ` David Barr
2012-02-07 8:58 ` Emanuele Zattin
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='CALts4TT49VAWPZ6XO9qahDTu=2E425QcRvXx5-75Jv8n4yp8RA@mail.gmail.com' \
--to=mdg149@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=joshua.redstone@fb.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.
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).