On Mon, Sep 01, 2008 at 04:19:47PM -0700, Junio C Hamano wrote: > I've pushed a sample repository that future git.git might look like to: > > http://repo.or.cz/w/git/split-submodule.git/ Holy pack count, Batman! On a whim, I cloned this via http (by switching /w/ to /r/). It took 7m13s. Cloning by git://, for comparison, took 1m31s. I pulled down 82 separate packs (and curiously, 277 separate .idx files). I know it is nice to keep the packs somewhat split for dumb transport users (since they otherwise have to pull down the whole thing), but I think it is coming here at the cost of first-time cloners (and yes, obviously I should have used --reference to an existing git clone; but for many that will not be an option). It looks like the gc.autopacklimit defaults to 50, which would have helped this. Pasky, is repo.or.cz not gc-ing? Or gc-ing with different parameters? Or is this an artifact of the forking infrastructure (i.e., these packs are actually split across multiple modules)? -Peff -- 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
