On Wed, May 09 2018, Stefan Beller wrote:
> Hi Christian,
>
> On Wed, May 9, 2018 at 7:33 AM, Christian Couder
> <christian.couder@xxxxxxxxx> wrote:
>> Hi,
>>
>> I might start working on implementing reftable in Git soon.
>
> Cool! Everyone is waiting for it as they dream about the
> performance and correctness benefits this brings.
>
> Benefits that I know of:
> * performance in repos with many refs
> * no capitalization issues on case insensitive FS
> * replay-ability of the last fetch ("show the last reflog
> of any ref under refs/remote/origin") is easier to do
> in a correct way. (This is one of my motivations to desire reftables)
> * We *might* be able to use reftables in negotiation later
> ("client: Last I fetched, you said your latest transaction
> number was '5' with the hash over all refs to be <sha1>;
> server: ok, here are the refs and the pack, you're welcome").
>
> Why are you (or rather booking.com) interested in this?
We have a lot of refs, which is a longer-term scalability issue (which
I've implemented hacks around (ref archiving)), and we also run into the
capitalization issues you mentioned.
