Issue metadata
Sign in to add a comment
|
23.3%-23.4% regression in loading.mobile at 453179:453211 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8984594408213940320
,
Mar 20 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/https___m.baidu.com_s?word_%E9%B2%9C%E8%8A%B1%E9%80%9F%E9%80%92_oq_%E9%B2%9C%E8%8A%B1 Revision Result N chromium@453178 43256.8 +- 1826.14 21 good chromium@453211 42976.5 +- 2283.78 21 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=https...m.baidu.com.s.word..E9.B2.9C.E8.8A.B1.E9.80.9F.E9.80.92.oq..E9.B2.9C.E8.8A.B1 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8984594408213940320 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4944452411457536 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Mar 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8984582560085499616
,
Mar 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8984506059389777408
,
Mar 22 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: c1d8534674a4bd63cea78b2a8d674623b6f889c7 bad_revision : 3bd6163bf8124714cdbcbf34789fb5206e67a636 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/Regular-3G/https___m.baidu.com_s?word_%E9%B2%9C%E8%8A%B1%E9%80%9F%E9%80%92_oq_%E9%B2%9C%E8%8A%B1 Revision Result N chromium@453113 43714.3 +- 1013.53 14 good chromium@453155 43415.2 +- 2169.66 14 bad chromium@453211 43474.4 +- 2364.34 14 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=https...m.baidu.com.s.word..E9.B2.9C.E8.8A.B1.E9.80.9F.E9.80.92.oq..E9.B2.9C.E8.8A.B1 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8984582560085499616 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5824870241271808 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Mar 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/https___m.baidu.com_s?word_%E9%B2%9C%E8%8A%B1%E9%80%9F%E9%80%92_oq_%E9%B2%9C%E8%8A%B1 Revision Result N chromium@453178 43110.2 +- 1700.52 21 good chromium@453211 43065.8 +- 3054.28 21 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=https...m.baidu.com.s.word..E9.B2.9C.E8.8A.B1.E9.80.9F.E9.80.92.oq..E9.B2.9C.E8.8A.B1 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8984506059389777408 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5091795374964736 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Apr 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982675077040487568
,
Apr 10 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstContentfulPaint_avg/Regular-3G/https___m.baidu.com_s?word_%E9%B2%9C%E8%8A%B1%E9%80%9F%E9%80%92_oq_%E9%B2%9C%E8%8A%B1 Revision Result N chromium@453178 43387.5 +- 2595.61 21 good chromium@453211 43434.4 +- 1629.06 21 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=https...m.baidu.com.s.word..E9.B2.9C.E8.8A.B1.E9.80.9F.E9.80.92.oq..E9.B2.9C.E8.8A.B1 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982675077040487568 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4944452411457536 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982651992268594624
,
Jun 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977863034688743872
,
Jun 3 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/Regular-3G/https___m.baidu.com_s?word_%E9%B2%9C%E8%8A%B1%E9%80%9F%E9%80%92_oq_%E9%B2%9C%E8%8A%B1 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=https...m.baidu.com.s.word..E9.B2.9C.E8.8A.B1.E9.80.9F.E9.80.92.oq..E9.B2.9C.E8.8A.B1 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977863034688743872 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6314678768107520 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jun 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977808391462314944
,
Jun 4 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/Regular-3G/https___m.baidu.com_s?word_%E9%B2%9C%E8%8A%B1%E9%80%9F%E9%80%92_oq_%E9%B2%9C%E8%8A%B1 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=https...m.baidu.com.s.word..E9.B2.9C.E8.8A.B1.E9.80.9F.E9.80.92.oq..E9.B2.9C.E8.8A.B1 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977808391462314944 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6314678768107520 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jun 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976993706687135648
,
Jun 13 2017
=== Auto-CCing suspected CL author rogerm@chromium.org === Hi rogerm@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : rogerm Commit : 2233a4a7cb12ac4acdebd33491b528f8fb670f02 Date : Mon Feb 27 23:11:16 2017 Subject: [translate] Add translate ranker model loader. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : loading.mobile Metric : timeToFirstMeaningfulPaint_avg/Regular-3G/https___m.baidu.com_s?word_%E9%B2%9C%E8%8A%B1%E9%80%9F%E9%80%92_oq_%E9%B2%9C%E8%8A%B1 Change : 12.55% | 43644.0076667 -> 49122.1885 Revision Result N chromium@453000 43644.0 +- 640.672 6 good chromium@453250 43756.5 +- 715.665 6 good chromium@453375 43707.1 +- 571.364 6 good chromium@453377 43865.7 +- 701.328 6 good chromium@453378 48540.8 +- 3642.03 6 bad <-- chromium@453379 49024.6 +- 1124.4 6 bad chromium@453383 49127.5 +- 703.013 6 bad chromium@453391 48616.1 +- 1765.77 6 bad chromium@453407 49108.8 +- 1677.47 6 bad chromium@453438 48983.3 +- 936.215 6 bad chromium@453500 48982.7 +- 1937.75 6 bad chromium@454000 49122.2 +- 1098.52 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=https...m.baidu.com.s.word..E9.B2.9C.E8.8A.B1.E9.80.9F.E9.80.92.oq..E9.B2.9C.E8.8A.B1 loading.mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976993706687135648 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4989632267157504 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jun 13 2017
This culprit change has been reverted and refactored to mitigate perf impacts. Monitoring |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Mar 20 2017