Re: Git is not scalable with too many refs/*

From: Martin Fick <mfick@codeaurora.org>
Date: Sep 26, 2011, 16:38 UTC
Message-ID: <201109261038.34527.mfick@codeaurora.org>
In-Reply-To: <CAGdFq_hRmSif4=V+9h8=S1fWfPCj+meRY8xGyfgv=SWk+DrBQw@mail.gmail.com>

On Monday, September 26, 2011 09:56:50 am Sverre Rabbelier wrote:

> Heya,
> 
> On Mon, Sep 26, 2011 at 17:48, Martin Fick

<mfick@codeaurora.org> wrote:

Show 12 quoted lines

> > Hmm, I was thinking that too, and I just did a test.
> > 
> > Instead of storing the changes under refs/changes, I
> > fetched them under refs/heads/changes and then ran git
> > 1.7.6 and it took about 3 mins.  Then, I ran the
> > 1.7.7.rc0.73 with
> > c774aab98ce6c5ef7aaacbef38da0a501eb671d4 reverted and
> > it only took 13s!  So, if this indeed tests what you
> > were suggesting, I think it shows that even in the
> > intended case this change slowed things down?
> 
> And if you run 1.7.7 without that commit reverted?

Sorry, I probably confused things by mentioning 1.7.6, the bad commit was way before that early 1.5 days...

As for 1.7.7, I don't think that exists yet, so did you mean the 1.7.7.rc0.73 version that I mentioned above without the revert? Strangely enough, that ends up being 1.7.7.rc0.72.g4b5ea. That is also slow with refs/heads/changes > 3mins.

-Martin

-- 
Employee of Qualcomm Innovation Center, Inc. which is a 
member of Code Aurora Forum