Mozilla repositories suitable for performance analysis

Gregory Szorc gregory.szorc at gmail.com
Wed Jan 14 22:16:32 UTC 2015


A lot of commits are starting to reference the mozilla-central repository
for performance impact. As a Mozillian, I love this trend!

I wanted to let people know of other Mozilla repositories suitable for
testing performance impact.

https://hg.mozilla.org/mozilla-central/ is what you've been using. It's the
mainline of Firefox development. But it only has 1 open branch head and 39
topological heads (which should probably get merged at some point).

If you are after many topological heads or tags, clone
https://hg.mozilla.org/releases/mozilla-beta. This repository tracks the
Firefox Beta releases. Each release (for reasons I don't wish to explain
nor make attempts to justify because I can't) creates a new "release"
branch and tag. This repository currently has 594 non-closed heads and 642
topological heads. There are 1623 tags across 1421 revisions to .hgtags. If
you cause branch or tags cache invalidation on this repository, you are
going to have a bad time.

If you want a repository with lots of interleaved commits between heads,
clone https://hg.mozilla.org/users/gszorc_mozilla.com/gecko-aggregate/.
This is an aggregate of most of the Firefox-related repositories. It has
994 non-closed heads and 1070 topological heads. There are 2708 tags. The
repository was created by "playing back" the push history of all the
disparate repositories since their inceptions as early as 2007. Revlog
order is essentially push order across all of Mozilla. This repository is
currently stored on the server in generaldelta because manifest delta
explosion is too painful otherwise. hg.mozilla.org is not yet running
bundle2, so cloning it will take forever. I can probably make a bundle
available upon request.

We may make a push towards aggressively closing branches and merging heads
in the next few months (for performance reasons). I can't guarantee the
gecko-aggregate repository will exist at that URL forever: we want to make
unified repositories more of an official thing, but that is probably
blocked on bundle2. If you are reading this in the future and things have
changed, reply and I'll try to steer you in the right direction.

Gregory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20150114/678950fd/attachment.html>


More information about the Mercurial-devel mailing list