Issue metadata
Sign in to add a comment
|
14% regression in tracing.tracing_with_debug_overhead at 491933:491975 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971725833505870592
,
Aug 9 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_air_perf_bisect Benchmark : tracing.tracing_with_debug_overhead Metric : peak_event_size_rate_avg/peak_event_size_rate_avg Revision Result N chromium@491932 5879637 +- 882825 21 good chromium@491975 5893810 +- 800252 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests tracing.tracing_with_debug_overhead More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971725833505870592 For feedback, file a bug with component Speed>Bisection
,
Sep 18 2017
Bisect doesn't repro. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 9 2017