[PATCH 2 of 2] setdiscovery: stop limiting the number of local head we initially send
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Wed Apr 17 06:36:48 EDT 2019
On 4/17/19 5:59 AM, Martin von Zweigbergk wrote:
>
>
> On Tue, Apr 16, 2019 at 11:41 AM Pierre-Yves David
> <pierre-yves.david at ens-lyon.org <mailto:pierre-yves.david at ens-lyon.org>>
> wrote:
>
> # HG changeset patch
> # User Pierre-Yves David <pierre-yves.david at octobus.net
> <mailto:pierre-yves.david at octobus.net>>
> # Date 1555428398 -7200
> # Tue Apr 16 17:26:38 2019 +0200
> # Node ID ffaa98def33a903f132ec4177d36823a741b6ef6
> # Parent 017778a4463a8e6ecb4b17cacf46a3ab27bdb239
> # EXP-Topic discovery-speedup
> # Available At https://bitbucket.org/octobus/mercurial-devel/
> # hg pull
> https://bitbucket.org/octobus/mercurial-devel/ -r ffaa98def33a
> setdiscovery: stop limiting the number of local head we initially send
>
>
> I think I tried something like this before. I still have a commit in my
> repo. I don't remember why I didn't send it. Perhaps the issue was that
> the heads are sent in HTTP headers and we need to limit the size of
> those to work with restrictive proxies and servers?
My intuition is that we are going to it that limit later anyway (eg: in
the getbundle common parameters).
What is our way forward here? This provide a large boost that I would
rather have in 5.0 core instead of having to patch it all around. Should
we hide the behavior behind a config as a start?
Cheers,
--
Pierre-Yves David
More information about the Mercurial-devel
mailing list