track_discovery: benchmark running perfdiscovery
This is using the same stripped clone as benchmarks for incoming/outgoing There are two different benchmark, one for a case where the source in a superset or the remote, one for case where the source in a subset of the remote. A third option where there are exclusive changeset on both side will be implemented later. Side note: perfdiscovery has been introduced in Mercurial public changeset db6cace18765 The pure 'subset' case is interesting, because that's what a CI bot does all the time. It's more generally the point of interest for VCS-based distribution, such as sets of tools etc. (Later on, we shall introduce a 'mixed' case, where both repos have heads that their peer doens't know of.)
Loading
Please register or sign in to comment