Joshua Redstone <joshua.redstone <at> fb.com> writes: > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html