Issue metadata
Sign in to add a comment
|
20.8% regression in system_health.common_mobile at 495370:495475 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969912479677828528
,
Aug 29 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Khushal Commit : 4ad05f3ae24fedcb1fc0438787d2ba4a5c61e520 Date : Thu Aug 17 23:13:43 2017 Subject: cc: Use src_rect for checker-imaging size veto. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : system_health.common_mobile Metric : timeToFirstPaint_avg/browse_chrome/browse_chrome_newtab Change : 17.55% | 603.7594 -> 709.719866667 Revision Result N chromium@495369 603.759 +- 26.951 6 good chromium@495371 600.084 +- 34.5225 6 good chromium@495372 702.325 +- 50.2732 6 bad <-- chromium@495373 705.639 +- 29.8646 6 bad chromium@495376 699.976 +- 23.896 6 bad chromium@495383 704.66 +- 38.0823 6 bad chromium@495396 705.061 +- 19.0432 6 bad chromium@495422 696.993 +- 99.0969 6 bad chromium@495475 709.72 +- 58.496 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=browse.chrome.newtab system_health.common_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8969912479677828528 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 29 2017