##// END OF EJS Templates
copies: move from a copy on branchpoint to a copy on write approach...
copies: move from a copy on branchpoint to a copy on write approach Before this changes, any branch points results in a copy of the dictionary containing the copy information. This can be very costly for branchy history with few rename information. Instead, we take a "copy on write" approach. Copying the input data only when we are about to update them. In practice we where already doing the copying in half of these case (because `_chain` makes a copy), so we don't add a significant cost here even in the linear case. However the speed up in branchy case is very significant. Here are some timing on the pypy repository. revision: large amount; added files: large amount; rename small amount; c3b14617fbd7 9ba6ab77fd29 before: ! wall 1.399863 comb 1.400000 user 1.370000 sys 0.030000 (median of 10) after: ! wall 0.766453 comb 0.770000 user 0.750000 sys 0.020000 (median of 11) revision: large amount; added files: small amount; rename small amount; c3b14617fbd7 f650a9b140d2 before: ! wall 1.876748 comb 1.890000 user 1.870000 sys 0.020000 (median of 10) after: ! wall 1.167223 comb 1.170000 user 1.150000 sys 0.020000 (median of 10) revision: large amount; added files: large amount; rename large amount; 08ea3258278e d9fa043f30c0 before: ! wall 0.242457 comb 0.240000 user 0.240000 sys 0.000000 (median of 39) after: ! wall 0.211476 comb 0.210000 user 0.210000 sys 0.000000 (median of 45) revision: small amount; added files: large amount; rename large amount; df6f7a526b60 a83dc6a2d56f before: ! wall 0.013193 comb 0.020000 user 0.020000 sys 0.000000 (median of 224) after: ! wall 0.013290 comb 0.010000 user 0.010000 sys 0.000000 (median of 222) revision: small amount; added files: large amount; rename small amount; 4aa4e1f8e19a 169138063d63 before: ! wall 0.001673 comb 0.000000 user 0.000000 sys 0.000000 (median of 1000) after: ! wall 0.001677 comb 0.000000 user 0.000000 sys 0.000000 (median of 1000) revision: small amount; added files: small amount; rename small amount; 4bc173b045a6 964879152e2e before: ! wall 0.000119 comb 0.000000 user 0.000000 sys 0.000000 (median of 8023) after: ! wall 0.000119 comb 0.000000 user 0.000000 sys 0.000000 (median of 7997) revision: medium amount; added files: large amount; rename medium amount; c95f1ced15f2 2c68e87c3efe before: ! wall 0.201898 comb 0.210000 user 0.200000 sys 0.010000 (median of 48) after: ! wall 0.167415 comb 0.170000 user 0.160000 sys 0.010000 (median of 58) revision: medium amount; added files: medium amount; rename small amount; d343da0c55a8 d7746d32bf9d before: ! wall 0.036820 comb 0.040000 user 0.040000 sys 0.000000 (median of 100) after: ! wall 0.035797 comb 0.040000 user 0.040000 sys 0.000000 (median of 100) The extra cost in the linear case can be reclaimed later with some extra logic. Differential Revision: https://phab.mercurial-scm.org/D7124

File last commit:

r43346:2372284d default
r43594:ffd04bc9 default
Show More
catapipe.py
121 lines | 3.6 KiB | text/x-python | PythonLexer
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 #!/usr/bin/env python3
#
# Copyright 2018 Google LLC.
#
# This software may be used and distributed according to the terms of the
# GNU General Public License version 2 or any later version.
"""Tool read primitive events from a pipe to produce a catapult trace.
Kyle Lippincott
catapult: add a bit more documentation on how to use catapult tracing...
r40526 Usage:
Terminal 1: $ catapipe.py /tmp/mypipe /tmp/trace.json
Terminal 2: $ HGCATAPULTSERVERPIPE=/tmp/mypipe hg root
<ctrl-c catapipe.py in Terminal 1>
$ catapult/tracing/bin/trace2html /tmp/trace.json # produce /tmp/trace.html
<open trace.html in your browser of choice; the WASD keys are very useful>
(catapult is located at https://github.com/catapult-project/catapult)
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 For now the event stream supports
START $SESSIONID ...
and
END $SESSIONID ...
events. Everything after the SESSIONID (which must not contain spaces)
is used as a label for the event. Events are timestamped as of when
they arrive in this process and are then used to produce catapult
traces that can be loaded in Chrome's about:tracing utility. It's
important that the event stream *into* this process stay simple,
because we have to emit it from the shell scripts produced by
run-tests.py.
Typically you'll want to place the path to the named pipe in the
HGCATAPULTSERVERPIPE environment variable, which both run-tests and hg
Kyle Lippincott
catapult: add a bit more documentation on how to use catapult tracing...
r40526 understand. To trace *only* run-tests, use HGTESTCATAPULTSERVERPIPE instead.
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 """
from __future__ import absolute_import, print_function
import argparse
import json
import os
Boris Feld
contrib: use a monotonic timer in catapipe...
r39550 import timeit
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288
_TYPEMAP = {
'START': 'B',
'END': 'E',
Augie Fackler
catapipe: add support for COUNTER events...
r42675 'COUNTER': 'C',
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 }
_threadmap = {}
Boris Feld
contrib: use a monotonic timer in catapipe...
r39550 # Timeit already contains the whole logic about which timer to use based on
# Python version and OS
timer = timeit.default_timer
Augie Fackler
formatting: blacken the codebase...
r43346
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 def main():
parser = argparse.ArgumentParser()
Augie Fackler
formatting: blacken the codebase...
r43346 parser.add_argument(
'pipe',
type=str,
nargs=1,
help='Path of named pipe to create and listen on.',
)
parser.add_argument(
'output',
default='trace.json',
type=str,
nargs='?',
help='Path of json file to create where the traces ' 'will be stored.',
)
parser.add_argument(
'--debug',
default=False,
action='store_true',
help='Print useful debug messages',
)
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 args = parser.parse_args()
fn = args.pipe[0]
os.mkfifo(fn)
try:
with open(fn) as f, open(args.output, 'w') as out:
out.write('[\n')
Boris Feld
contrib: use a monotonic timer in catapipe...
r39550 start = timer()
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 while True:
ev = f.readline().strip()
if not ev:
continue
Boris Feld
contrib: use a monotonic timer in catapipe...
r39550 now = timer()
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 if args.debug:
print(ev)
verb, session, label = ev.split(' ', 2)
if session not in _threadmap:
_threadmap[session] = len(_threadmap)
Augie Fackler
catapipe: add support for COUNTER events...
r42675 if verb == 'COUNTER':
amount, label = label.split(' ', 1)
payload_args = {'value': int(amount)}
else:
payload_args = {}
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 pid = _threadmap[session]
Augie Fackler
catapipe: fix bug introduced when switching to the timer api...
r39971 ts_micros = (now - start) * 1000000
Augie Fackler
formatting: blacken the codebase...
r43346 out.write(
json.dumps(
{
"name": label,
"cat": "misc",
"ph": _TYPEMAP[verb],
"ts": ts_micros,
"pid": pid,
"tid": 1,
"args": payload_args,
}
)
)
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 out.write(',\n')
finally:
os.unlink(fn)
Augie Fackler
formatting: blacken the codebase...
r43346
Augie Fackler
contrib: new script to read events from a named pipe and emit catapult traces...
r39288 if __name__ == '__main__':
main()