Building a benchmark reference repository with obsolescence

[Pierre-Yves David]

Hi everyone,

TL;DR: please send me tarball of your mercurial-core development repository

A current shortcoming of the benchmark suite is that all repository 
contains public changeset only. I would like to fix this by adding a 
repository with draft changesets and obsolescence markers.

Having such repository would help:
- assess the current performance situation about obsolescence and filtered,
- confirm that patches achieve their promissed performance improvement,
- detect regression on this logic.

Each new reference repository in the benchmark increase the execution 
time. So I would like this new reference to be as "interesting" and 
"diverse" as possible. I would like to simulate some heavily used 
development repository and so I intend to combine as much obsolescence 
markers and draft as possible.

I already combine my own repository with hg-comitted and with the 
various `mercurial-devel` repository octobus uses for synchronisation. 
However, I would like to gather more intermediate changesets and changes 
from a more diverse set of users. So please, if possible, share your 
personal mercurial development repository with me. I'll do the combining.

For those curious, the current state is available here: 
https://www.mercurial-scm.org/repo/users/marmoute/reference-filtered-mercurial/

You might have been CCed in this email, this is because I suspect you 
are likely to have interesting local repository.

Cheers,

-- 
Pierre-Yves David