From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Jonathan Tan <jonathantanmy@google.com>
Subject: Re: Implementing reftable in Git
Date: Wed, 09 May 2018 20:52:50 +0200 [thread overview]
Message-ID: <874ljgy83h.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <CAGZ79kZx=wHKc=2WLz-8pQWv1VhRq+pKVV9=Shq3gEMdkX-Q=A@mail.gmail.com>
On Wed, May 09 2018, Stefan Beller wrote:
> 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.
next prev parent reply other threads:[~2018-05-09 18:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 14:33 Implementing reftable in Git Christian Couder
2018-05-09 14:52 ` Derrick Stolee
2018-05-09 16:07 ` Duy Nguyen
2018-05-09 16:48 ` Jonathan Nieder
2018-05-09 17:51 ` Carlos Martín Nieto
2018-05-09 17:54 ` Jonathan Nieder
2018-05-09 18:05 ` Carlos Martín Nieto
2018-05-09 17:42 ` Stefan Beller
2018-05-09 17:48 ` Jonathan Nieder
2018-05-09 17:55 ` Stefan Beller
2018-05-09 18:52 ` Ævar Arnfjörð Bjarmason [this message]
2018-05-11 9:31 ` Michael Haggerty
2018-05-11 22:21 ` David Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874ljgy83h.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).