Repo with many obsolescence markers is getting really slow
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Wed Mar 29 11:10:53 UTC 2017
On 03/29/2017 01:08 PM, Pierre-Yves David wrote:
>
>
> On 03/28/2017 10:57 PM, Dominik Ruf wrote:
>> Hi,
>>
>> I was using changeset evolution quite heavily. (more then 20000
>> obsolescence markers, a lot of amend and rebasing)
>> And I noticed that pulling and pushing is getting really slow.
>> Is this a know issue? Could I expect that this is getting improved in
>> the future?
>
> Yes, the current protocol to discover marker is very basic, have many
> known short coming and lack caching. We have various idea for a better
> protocol and caching, a first prototype for it should ship in the the
> future version 6.0.0 of evolve (to be released soon). So we should
> eventually have a proper version of the protocol done for good.
>
> In addition there is some additional caching around obsolescence markers
> that should happen in the near future to speed up local operation.
>
> Cheers,
In addition, can you tell me a bit more about your repo:
* number of changesets total
* number of visible changesets
* number of public changesets
* number of markers
* output of `hg debugobsstorestat`
* set `experimental.verbose-obsolescence-exchange=1` in your config
* output of a push and pull with --debug
--
Pierre-Yves David
More information about the Evolve-testers
mailing list