3 ms·
Alas neither can support effective work in large repositories: at my day job we have about 100gb repository (just one branch), but most people only use 4Gb at a
by DenisM 18y ago
Alas neither can support effective work in large repositories: at my day job we have about 100gb repository (just one branch), but most people only use 4Gb at a time. Except the build servers - they get the most of the stuff at once. Perforce lets you create partial enlistment and only get the 4gb you need, while both Git and Hg require pulling entire 100Gb over the network.
There's been very little progress on these issues as well - both communities seem to be content with relatively small repositories. Sad.
- thorax 18y agoI'm also a big fan of Perforce for large (especially internal) repositories. It handles just about everything smoothly and is also free for Open Source. That being said, I've really been enjoying working with Mercurial. I think the biggest shortcoming I feel is not being able to branch (easily?) subdirectories rather than repositories.
- utx00 18y agoyou may want to take a look at http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html http://www.kernel.org/pub/software/scm/git/docs/git-submodul.... mercurial lacks this as of now.
- bretthoerner 18y agoMercurial has extension support, and one of them (used for example on the OpenJDK project - a "real" project of some size) is "Forest", which does just that: http://www.bitbucket.org/pmezard/hgforest-crew/overview/ http://www.bitbucket.org/pmezard/hgforest-crew/overview/
- DenisM 18y agothere is no documentation at all...
- anthonyb 18y agoMost things can be found on the Mercurial repository: http://www.selenic.com/mercurial/wiki/index.cgi/ForestExtension http://www.selenic.com/mercurial/wiki/index.cgi/ForestExtens... Not sure why there are no docs in the hgforest repository though - that seems like a pretty big oversight.
- bd 18y agoOh yeah. They both also fail miserably on few large files (hundreds of megabytes). I did tests with 100-200 MB ascii text files and good old Subversion beat both Git and Mercurial easily. Git was better, just several times slower than SVN. For Hg, I had to kill the process.
- tlrobinson 18y agoJeebus. I'm curious what a 100GB branch contains? Data? Binaries? Images?
- DenisM 18y agoBasically, it's everything that goes into the product. 1. source code 2. toolchain. there are good reasons for it - we had enromous problems with people using outdated toolchains and fighting with obscure compiler bugs. also just installing new toolchain for everyone will not work - it may have new bugs which are only triggered by old code. bottom line is that toolchain must be in sync with the source and it was a painful lesson. I must add that we have dozens if not hundreds of branches. 3. tests. tests must be in sync with the code, and are branched/merged together. a lot of tests. 4. test results. must be in sync with tests and branched/merged together. So there you have it. Other people I know who also have large repsitories are art studios who want to version their artwork - they store raw images.
- qaexl 18y agoGNOME and Xfree86 are huge git repositories. They "solved" the problem by using git submodules and their project has already been broken down into modules already. I'm not entirely satisfied with this approach, since it means a brand new developer has to figure out how to pull all the submodules down when setting up his dev environment.