[PATCH 2 of 9 V3] perf: offer full details in perfrevlogwrite
Boris Feld
boris.feld at octobus.net
Tue Nov 6 11:27:30 UTC 2018
# HG changeset patch
# User Boris Feld <boris.feld at octobus.net>
# Date 1538557497 -7200
# Wed Oct 03 11:04:57 2018 +0200
# Node ID fd1ce4514534dc539c2f00afb4340e0ae575d30f
# Parent 1d1bc06187e9296430045aa39c3d3e2d12f61875
# EXP-Topic revlog-perf
# Available At https://bitbucket.org/octobus/mercurial-devel/
# hg pull https://bitbucket.org/octobus/mercurial-devel/ -r fd1ce4514534
perf: offer full details in perfrevlogwrite
This will be useful for people who want to study the timing pattern more
closely.
diff --git a/contrib/perf.py b/contrib/perf.py
--- a/contrib/perf.py
+++ b/contrib/perf.py
@@ -1571,6 +1571,7 @@ def perfrevlogrevisions(ui, repo, file_=
[(b's', b'startrev', 1000, b'revision to start writing at'),
(b'', b'stoprev', -1, b'last revision to write'),
(b'', b'count', 3, b'last revision to write'),
+ (b'', b'details', False, b'print timing for every revisions tested'),
],
b'-c|-m|FILE')
def perfrevlogwrite(ui, repo, file_=None, startrev=1000, stoprev=-1, **opts):
@@ -1610,6 +1611,13 @@ def perfrevlogwrite(ui, repo, file_=None
fm = ui.formatter(b'perf', opts)
displayall = ui.configbool(b"perf", b"all-timing", False)
+ # print individual details if requested
+ if opts['details']:
+ for idx, item in enumerate(results, 1):
+ rev, data = item
+ title = 'revisions #%d of %d, rev %d' % (idx, resultcount, rev)
+ formatone(fm, data, title=title, displayall=displayall)
+
# sorts results by median time
results.sort(key=lambda x: sorted(x[1])[len(x[1]) // 2])
# list of (name, index) to display)
More information about the Mercurial-devel
mailing list