On Wed, Feb 12, 2014 at 9:02 AM, Robin H. Johnson <robbat2@xxxxxxxxxx> wrote: > On Tue, Feb 11, 2014 at 05:54:51PM -0800, Stefan Zager wrote: >> We in the chromium project have a keen interest in adding threading to >> git in the pursuit of performance for lengthy operations (checkout, >> status, blame, ...). Our motivation comes from hitting some >> performance walls when working with repositories the size of chromium >> and blink: > +1 from Gentoo on performance improvements for large repos. > > The main repository in the ongoing Git migration project looks to be in > the 1.5GB range (and for those that want to propose splitting it up, we > have explored that option and found it lacking), with very deep history > (but no branches of note, and very few tags). >From v1.9 shallow clone should work for all push/pull/clone... so history depth does not matter (on the client side). As for gentoo-x86's large worktree, using index v4 and avoid full-tree operations (e.g. "status .", not "status"..) should make all operations reasonably fast. I plan to make "status" fast even without path limiting with the help of inotify, but that's not going to be finished soon. Did I miss anything else? -- Duy -- 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