Issue metadata
Sign in to add a comment
|
58.3% regression in loading.mobile at 514572:514641 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963319717887781376
,
Nov 12 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/warm/FlipKart Revision Result N chromium@514571 159.259 +- 32.4194 21 good chromium@514641 155.614 +- 29.8034 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=FlipKart loading.mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963319717887781376 For feedback, file a bug with component Speed>Bisection
,
Nov 13 2017
Looks like we reverted to the previous average. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 10 2017