Re: Performance issue: initial git clone causes massive repack

From: Nicolas Pitre <nico@cam.org>
Date: Apr 6, 2009, 03:24 UTC
Message-ID: <alpine.LFD.2.00.0904052315210.6741@xanadu.home>
In-Reply-To: <fabb9a1e0904051436i1dc9c1bdhe86a23e470c756f9@mail.gmail.com>

On Sun, 5 Apr 2009, Sverre Rabbelier wrote:

Show 12 quoted lines

> Heya,
> 
> On Sun, Apr 5, 2009 at 23:28,  <david@lang.hm> wrote:
> > Guys, back off a little on telling the gentoo people to change.
> 
> I agree here, we should either say "look, we don't really support big
> repositories because [explanation here], unless you [workarounds
> here]" OR we should work to improve the support we do have. Of course,
> the latter option does not magically create developer time to work on
> that, but if we do go that way we should at least tell people that we
> are aware of the problems and that it's on the global TODO list (not
> necessarily on anyone's personal TODO list though).

For the record... I at least am aware of the problem and it is indeed on my personal git todo list. Not that I have a clear solution yet (I've been pondering on some git packing issues for almost 4 years now).

Still, in this particular case, the problem appears to be unclear to me, like "this shouldn't be so bad".

> Of course, the problem can sometimes be solved by splitting the
> repository, but I think it is important to have an official policy
> here, do we want Git to support huge repositories, or do we not?

I do.

Nicolas