# HG changeset patch
# User Boris Feld <boris.feld@octobus.net>
# Date 1548668860 18000
# Node ID d65ba1ff45592366a305fa27b38d09a38fbf479c
# Parent  ab6d1f82be32dbeef7981f3e10b84c5ea85698e0
perf: add some documentation to perfindex

It seems useful to document how the arguments can affect the benchmark.

diff -r ab6d1f82be32 -r d65ba1ff4559 contrib/perf.py
--- a/contrib/perf.py	Fri Jan 25 14:53:19 2019 -0500
+++ b/contrib/perf.py	Mon Jan 28 04:47:40 2019 -0500
@@ -1017,6 +1017,14 @@
             (b'', b'rev', b'', b'revision to be looked up (default tip)'),
          ] + formatteropts)
 def perfindex(ui, repo, **opts):
+    """benchmark index creation time followed by a lookup
+
+    The default is to look `tip` up. Depending on the index implementation,
+    the revision looked up can matters. For example, an implementation
+    scanning the index will have a faster lookup time for `--rev tip` than for
+    `--rev 0`.
+
+    It is not currently possible to check for lookup of a missing node."""
     import mercurial.revlog
     opts = _byteskwargs(opts)
     timer, fm = gettimer(ui, opts)
diff -r ab6d1f82be32 -r d65ba1ff4559 tests/test-contrib-perf.t
--- a/tests/test-contrib-perf.t	Fri Jan 25 14:53:19 2019 -0500
+++ b/tests/test-contrib-perf.t	Mon Jan 28 04:47:40 2019 -0500
@@ -93,7 +93,7 @@
                  find statistic about potential parameters for the
                  'perftracecopies'
    perfignore    benchmark operation related to computing ignore
-   perfindex     (no help text available)
+   perfindex     benchmark index creation time followed by a lookup
    perflinelogedits
                  (no help text available)
    perfloadmarkers