Next plans on radixlink and hash-preserving obsstore

Martin von Zweigbergk martinvonz at google.com
Mon Jul 10 18:39:31 EDT 2017


On Mon, Jul 10, 2017 at 3:36 PM, Jun Wu <quark at fb.com> wrote:
> Excerpts from Martin von Zweigbergk's message of 2017-07-10 15:28:07 -0700:
>> I think you have a good point. We only have exchange directly between
>> our clients and our server so far. I don't know if FB users do more
>> peer-to-peer exchanges. It's very easy to forget that we also need to
>> handle those cases well.
>
> The discussion seems to suggest that hash-preserving and exchange conflict
> with each other, or exchange code has to be rewritten from scratch with
> hash-preserving.

I didn't mean to suggest anything besides what I wrote :-) I was just
saying that it's something that I (and probably at least other
Googlers) tend to forget.

> That's untrue. Hash-preserving won't break exchange and the
> existing algorithm in core could largely be reused. Of course, clients need
> upgrade to understand the new format.
>
> Besides, I believe the new format has some nice parts to make it easier to
> optimize the exchange algorithm. I'll get into tech details when we start
> format discussion formally.

Great!


More information about the Mercurial-devel mailing list