Re: Git performance results on a large repository

From: Zeki Mokhtarzada <zeki@webs.com>
Date: Feb 4, 2012, 00:01 UTC
Message-ID: <loom.20120204T004543-798@post.gmane.org>
In-Reply-To: <CB5074CF.3AD7A%joshua.redstone@fb.com>

Show 5 quoted lines

> The test repo has 4 million commits, linear history and about 1.3 million
> files.  The size of the .git directory is about 15GB, and has been
> repacked with 'git repack -a -d -f --max-pack-size=10g --depth=100
> --window=250'.  This repack took about 2 days on a beefy machine (I.e.,
> lots of ram and flash).  The size of the index file is 191 MB. I can share

Are you willing to give up all or part of your history in your working repository? I've heard of larger projects starting from scratch (i.e. copy all of your files into a brand new repo.) You can keep your old repo around for archival purposes. Also, how much of your repo is code, versus static assets. You could move all of your static assets (images, css, maybe some js?) into another repo, and then merge the two repo's together at build time if you absolutely need them deployed together.

Here are a couple strategies for doing a partial truncate:

http://stackoverflow.com/questions/4515580/how-do-i-remove-the-old-history-from-a-git-repository http://bogdan.org.ua/2011/03/28/how-to-truncate-git-history-sample-script-included.html

-Zeki