New issue
Advanced search Search tips

Issue 781252 link

Starred by 1 user
Status: Duplicate
Merged: issue 780502
Owner: ----
Closed: Nov 2017
Cc:
mustaq@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.1%-45.5% regression in loading.mobile at 512425:512885

Project Member Reported by mustaq@chromium.org, Nov 3 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=781252

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=a458fc0c314abeda05d46dbca507168786d3a787d97859ddcc86c004233f7b93


Bot(s) for this bug's original alert(s):

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-webview-nexus5X
android-webview-nexus6
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 3 2017

Mergedinto: 780502
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Koji Ishii
  Commit : 811fe6a25ddee5065812bf50733de963e58832cb
  Date   : Tue Oct 31 14:34:37 2017
  Subject: Add CrashKey to LazyLineBreakIterator on Android

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : loading.mobile
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/Regular-3G/58Pic
  Change       : 7.08% | 605.478333333 -> 648.362833333

Revision             Result                  N
chromium@512824      605.478 +- 46.5881      6      good
chromium@512825      638.162 +- 43.4646      9      bad       <--
chromium@512826      643.026 +- 34.2652      9      bad
chromium@512828      649.799 +- 25.8672      6      bad
chromium@512832      643.355 +- 25.6027      6      bad
chromium@512840      647.972 +- 44.3626      6      bad
chromium@512855      641.954 +- 38.6515      9      bad
chromium@512885      648.363 +- 30.2638      6      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=58Pic loading.mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963934854948294816


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Koji Ishii
  Commit : 811fe6a25ddee5065812bf50733de963e58832cb
  Date   : Tue Oct 31 14:34:37 2017
  Subject: Add CrashKey to LazyLineBreakIterator on Android

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : loading.mobile
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/warm/DevOpera
  Change       : 7.91% | 189.683333333 -> 204.691

Revision             Result                  N
chromium@512803      189.683 +- 8.35744      6      good
chromium@512821      186.517 +- 9.19473      6      good
chromium@512824      189.814 +- 8.45544      6      good
chromium@512825      205.443 +- 2.5912       6      bad       <--
chromium@512826      206.174 +- 10.8856      6      bad
chromium@512830      210.336 +- 7.09081      6      bad
chromium@512839      212.675 +- 12.5783      6      bad
chromium@512875      204.691 +- 5.76355      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=DevOpera loading.mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963934838922524752


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Koji Ishii
  Commit : 811fe6a25ddee5065812bf50733de963e58832cb
  Date   : Tue Oct 31 14:34:37 2017
  Subject: Add CrashKey to LazyLineBreakIterator on Android

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : loading.mobile
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/Regular-3G/QQNews
  Change       : 53.19% | 880.126166667 -> 1348.258

Revision             Result                  N
chromium@512424      880.126 +- 39.7728      6      good
chromium@512637      890.365 +- 23.89        6      good
chromium@512743      889.385 +- 31.9947      6      good
chromium@512796      873.857 +- 28.9371      6      good
chromium@512823      884.71 +- 31.0554       6      good
chromium@512824      885.382 +- 40.4338      6      good
chromium@512825      1333.9 +- 169.371       6      bad       <--
chromium@512827      1334.23 +- 206.333      6      bad
chromium@512830      1370.76 +- 194.831      6      bad
chromium@512836      1385.51 +- 164.926      6      bad
chromium@512849      1348.26 +- 195.95       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=QQNews loading.mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963934922513813008


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment