git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Implementing reftable in Git

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 9, 2018, 18:52 UTC
Message-ID
<874ljgy83h.fsf@evledraar.gmail.com>
In-Reply-To
<CAGZ79kZx=wHKc=2WLz-8pQWv1VhRq+pKVV9=Shq3gEMdkX-Q=A@mail.gmail.com>
On Wed, May 09 2018, Stefan Beller wrote:
Show 23 quoted lines
> Hi Christian,
>
> On Wed, May 9, 2018 at 7:33 AM, Christian Couder
> <christian.couder@gmail.com> 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.

Previous: Stefan BellerNext: Michael Haggerty
Message 11 of 13 in “Implementing reftable in Git”
  1. Christian CouderMay 9, 2018
  2. Derrick StoleeMay 9, 2018
  3. Duy NguyenMay 9, 2018
  4. Jonathan NiederMay 9, 2018
  5. Carlos Martín NietoMay 9, 2018
  6. Jonathan NiederMay 9, 2018
  7. Carlos Martín NietoMay 9, 2018
  8. Stefan BellerMay 9, 2018
  9. Jonathan NiederMay 9, 2018
  10. Stefan BellerMay 9, 2018
  11. Ævar Arnfjörð BjarmasonMay 9, 2018
  12. Michael HaggertyMay 11, 2018
  13. David TurnerMay 11, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.