On Sun, Jul 25, 2010 at 5:40 AM, <skillzero@xxxxxxxxx> wrote: >>> (although just having all those objects in >>> the .git directory still slows it down quite a bit). >> >> You're the second person who has mentioned this today (the first one >> was to me in a private email). I'd like to understand this better. > > What I'm basing this on is that even when I'm using a sparse checkout > such that I have only a small subset of the files in my working > directory, git status seems singifncantly slower for me than an > equivalent git repository that only has that subset of files. That's > not very scientific, but that's what made me think just having a large > .git directory with lots of objects/history slows down git status even > if the working copy doesn't have a lot of files. Hmm... I recall I experienced some slower operations on webkit with sparse checkout too. > > I will try to experiment and see if I can narrow it down with some real numbers. Yes, I'd appreciate that. By the way, how hard is it to use git-replace to implement narrow clone? -- 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