OpenOffice.org is looking for a new SCM (Software Configuration Management) tool, or at least was on Friday, 19 Jan 2007; see: http://blogs.sun.com/GullFOSS/entry/openoffice_org_scm One of the SCMs considered is Git. One of others is Subversion. There is a functional git tree with the entire OOo history for testing purposes that can be found at: http://go-oo.org/git. What I am concerned about is some of git benchmark results at Git page on OpenOffice.org wiki: http://wiki.services.openoffice.org/wiki/Git#Comparison Actually it is comparison with CVS and Subversion, although most benchmarks are done only for git. In 'Size of data on the server' git has CVS beat hands down: 1.3G vs 8.5G for sources, 591M vs 1.1G for third party. I think it is similar for Subversion. I hope that repository is fully packed: IIRC the Mozilla CVS repository import was about 0.6GB pack file, not 1.3GB. The problem is with 'Size of checkout': to start working in repository one needs 1.4G (sources) and 98M (third party) for CVS checkout (it is 1.5G for sources for Subversion checkout). Ordinary for distributed SCM you would need size of repository + size of sources (working area), which is 2.8G for sources and 688M for third party stuff files you can hack on + the history]. This makes some prefer to go centralized SCM route, i.e. Subversion as replacement for CVS (+ CWS, ChildWorkSpace). What might help here is splitting repository into current (e.g. from OOo 2.0) and historical part, and / or using shallow clone. Implementing partial checkouts, i.e. checking out only part of working area (and using 'theirs' strategy for merging not-checked-out part for merges) would help. Splitting repository into submodules, and submodule support -- it depends on organization of OOo sources, would certainly help for third party stuff repository. 'Checkout time' (which should be renamed to 'Initial checkout time'), in which git also loses with 130 minutes (Linux, 2MBit DSL) [from go-oo.org], 100min (Linux, 2MBit DSL, Wireless, no proxy) [from go-oo.org] versus 117 minutes (Linux, 2MBit DSL), 26 minutes (Linux, 2MBit DSL, with compression (-z 6)) for CVS, and 60 Minutes (Windows, 34Mbit Line) for Subversion, would also be helped by the above. What I'm really concerned about is branch switch and merging branches, when one of the branches is an old one (e.g. unxsplash branch), which takes 3min (!) according to the benchmark. 13-25sec for commit is also bit long, but BRANCH SWITCHING which takes 3 MINUTES!? There is no comparison benchmark for CVS or Subversion, though... Comparison / benchmark lacks some crucial info, like what computer was used (CPU, RAM, HDD), what filesystem was used, git version etc. It does have commands used for tests (benchmarks). Could you confirm (or deny) those results? go-oo.org uses git 1.4.3.4; was there some improvement or bugfix related to the speed of checkout? -- Jakub Narebski ShadeHawk on #git Poland - 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