3 ms·
One thing I'm unclear on -- do you already have a really large Git repository which is getting too slow to use, or are you just contemplating building a repo th
by curtis 12y ago
One thing I'm unclear on -- do you already have a really large Git repository which is getting too slow to use, or are you just contemplating building a repo that will be that large and you think that it might be too large?
- ansible 12y agoWe've been trying to use git for this existing repository, but it is too slow to use, in part because it is too large in total size, or in number of files. Or both.
- curtis 12y agoI had a very nice write-up about how Git can efficiently handle much larger repositories than people think, but it sounds like it doesn't apply in your case. Something that might be worth trying: If you have a bunch of files that will very rarely ever change, you might try just putting them in a tar file and modify your build system to unpack them on demand. This may sound crazy, but in my experience it's not raw file size that gives Git problems, it's simply the file count. I don't know about the latest Git versions, but back in the 1.8 era when I was doing extensive testing, Git was notorious for doing a file-stat on every single checked out file every time you ran "git status". If you've got fewer files, regardless of size, your performance will likely be better. (The initial git clone is of course an exception.)