Re: Git performance results on a large repository
- From
- slinky <slinky@iki.fi>
- Date
- Feb 4, 2012, 08:57 UTC
- Message-ID
- <loom.20120204T094226-583@post.gmane.org>
- In-Reply-To
- <CB5074CF.3AD7A%joshua.redstone@fb.com>
Joshua Redstone <joshua.redstone <at> fb.com> writes:
Show 6 quoted lines
> The git performance we observed here is too slow for our needs. So the > question becomes, if we want to keep using git going forward, what's the > best way to improve performance. It seems clear we'll probably need some > specialized servers (e.g., to perform git-blame quickly) and maybe > specialized file system integration to detect what files have changed in a > working tree.
Hi Joshua,
sounds like you have everything in a single .git. Split up the massive repository to separate smaller .git repositories.
For example, Android code base is quite big. They use the repo tool to manage a number of separate .git repositories as one big aggregate "repository".
Cheers, Slinky