Mercurial > hg

view contrib/benchmarks/perf.py @ 30832:da5fa0f13a41

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
ui: introduce an experimental dict of exportable environment variables Care needs to be taken to prevent leaking potentially sensitive environment variables through hgweb, if template support for environment variables is to be introduced. There are a few ideas about the API for preventing accidental leaking [1]. Option 3 seems best from the POV of not needing to configure anything in the normal case. I couldn't figure out how to do that, so guard it with an experimental option for now. [1] https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-January/092383.html
author Matt Harbison <matt_harbison@yahoo.com>
date Tue, 17 Jan 2017 23:05:12 -0500
parents cff0f5926797
children 2372284d9457
line wrap: on
line source

# perf.py - asv benchmarks using contrib/perf.py extension
#
# Copyright 2016 Logilab SA <contact@logilab.fr>
#
# This software may be used and distributed according to the terms of the
# GNU General Public License version 2 or any later version.

from __future__ import absolute_import

from . import perfbench

@perfbench()
def track_tags(perf):
    return perf("perftags")

@perfbench()
def track_status(perf):
    return perf("perfstatus", unknown=False)

@perfbench(params=[('rev', ['1000', '10000', 'tip'])])
def track_manifest(perf, rev):
    return perf("perfmanifest", rev)

@perfbench()
def track_heads(perf):
    return perf("perfheads")