From: Dave Borowitz <dborowitz@google.com>
Date: Tue, 22 Dec 2015 17:04:12 GMT
Subject: Re: RefTree: Alternate ref backend
Message-ID: <CAD0k6qT21siw00XMM6fSz2d9dT1yiTMh5ai9_w=fFk9GKin83w@mail.gmail.com>
In-Reply-To: <CAJo=hJtPSxY1YZgEt1AA_ukgY9cTA=1tdv_F+nCetv_Ux9E=3g@mail.gmail.com>

On Tue, Dec 22, 2015 at 8:11 AM, Shawn Pearce <spearce@spearce.org> wrote:
> Yup, and Gerrit Code Review servers often have 100k+ refs per
> repository. We can't rewrite the entire store every time either. So
> its not a flat list. Its a directory structure using the / separators
> in the ref namespace.

I wonder if this might be insufficient in some cases, and additional
sharding might be required (though I haven't thought about how to do
that).

Chromium, for example, has upwards of 10k tags:
$ git ls-remote https://chromium.googlesource.com/chromium/src
refs/tags/\* | wc -l
8733

And I doubt it's unique in this regard.