Issue metadata
Sign in to add a comment
|
44.1% regression in tracing.tracing_with_debug_overhead at 495120:495354 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969999974232109440
,
Aug 28 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Charles Harrison Commit : 007abddf6ad7f7d3f1491217119e3e7166faaace Date : Thu Aug 17 21:39:49 2017 Subject: Testing config: doc.write blocking change on slow connections only Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : tracing.tracing_with_debug_overhead Metric : trace_size_avg/Wikipedia Change : 42.15% | 12873467.6667 -> 18299731.0 Revision Result N chromium@495119 12873468 +- 390514 6 good chromium@495237 13019166 +- 480880 6 good chromium@495296 13158244 +- 648717 6 good chromium@495325 13102394 +- 246200 6 good chromium@495326 13125846 +- 592130 6 good chromium@495327 18376982 +- 219202 6 bad <-- chromium@495329 18471289 +- 192647 6 bad chromium@495333 18381466 +- 289901 6 bad chromium@495340 18205794 +- 310817 6 bad chromium@495354 18299731 +- 329202 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Wikipedia 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/8969999974232109440 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 28 2017