On Wed, Sep 10, 2014 at 05:25:36PM +0700, Duy Nguyen wrote: > On Wed, Sep 10, 2014 at 3:13 PM, Jeff King <peff@xxxxxxxx> wrote: > > I was running pack-refs on a repository with a very large number of > > loose refs (about 1.8 million). Needless to say, this ran very slowly > > and thrashed the disk, as that's almost 7G using 4K inodes. But it did > > eventually generate a packed-refs file, at which point it tried to prune > > the loose refs. > > Urghh.. ref advertisment for fetch/push would be unbelievably large. > Gotta look at the "git protocol v2" again soon.. Yes, we don't let normal fetchers see these repos. They're only for holding shared objects and the ref tips to keep them reachable. So we never fetch from them, even locally. We only fetch to them from normal repos (and never push to or from them at all). It's still rather painful just to do normal things, though. Every git operation loads the whole packed-refs file into memory. I'm biding my time on the ref-backend patches that are being worked on. :) -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