Ensure that blink perf can accept more than just time. |
|||||
Issue descriptionRight now the blink perf system seems to only accept a single value (time taken) as a thing to measure. When migrating rasterize and record, we'll need more values to record. Ideally we can just spit out a json object that can be parsed by the python script to produce all of the values needed.
,
Jun 6 2017
,
Jun 9 2017
I think we should take this opportunity to refactor how blink_perf test results are output & integrated with Telemetry. Currently it's done very hackily in https://cs.chromium.org/chromium/src/tools/perf/benchmarks/blink_perf.py?q=blink_perf.py&dr&l=222 Summary of what those code does: telemetry parses the "log" element in the dom & output the data in that log. What it should do instead: blink_perf harness should store its results in a js dictionary, something like testRunner.testResults. Telemetry should just use evaluate that object to get the test results out.
,
Aug 31 2017
Design doc: https://docs.google.com/document/d/1YFw49ap4ovznC6FKo_hFTO418pu9HI3CLnuVFqq0msQ/edit# PTAL and let me know what you think
,
Aug 31 2017
,
Aug 31 2017
The design doc LGTM.
,
Sep 1 2017
LGTM with my admittedly not-much-context
,
Aug 2
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by vmp...@chromium.org
, Jun 6 2017