Issue metadata
Sign in to add a comment
|
75.2%-97.7% improvement in loading.mobile at 514808:515069 |
||||||||||||||||||||||
Issue descriptionSuspiciously large improvement, did something break?
,
Nov 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963304407087485472
,
Nov 10 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Caleb Rouleau Commit : 5daa21ce99f8f70abe1202689a510d9f03e5a3e1 Date : Wed Nov 08 23:25:07 2017 Subject: Have pages edit grouping keys themselves. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/Dawn Change : 54.90% | 3187.8205 -> 1437.805 Revision Result N chromium@514954 3187.82 +- 853.526 6 good chromium@514983 2957.99 +- 240.144 6 good chromium@514998 3205.87 +- 867.333 6 good chromium@514999 1487.81 +- 257.59 6 bad <-- chromium@515000 1537.04 +- 303.541 6 bad chromium@515002 1558.66 +- 180.933 6 bad chromium@515005 1452.14 +- 323.81 6 bad chromium@515012 1497.01 +- 332.811 6 bad chromium@515069 1437.8 +- 286.682 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=Dawn loading.mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963304407087485472 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 10 2017