New issue
Advanced search Search tips

Issue 781256 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

10%-26% regression in blink_perf.css at 512747:512997

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=781256

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


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

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 3 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: 15733e14e142d1b3fddf5dc1dc079cf57c5cc8bf
  bad_revision : 2883942de0ba902ff1928a91e889d0ce5dbe0a94

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : blink_perf.css
  Metric       : LoadSemanticPageExample/LoadSemanticPageExample

Revision             Result                  N
chromium@512803      348.425 +- 7.1          6      good
chromium@512816      339.071 +- 7.13036      6      good
chromium@512828      426.58 +- 14.9432       6      bad
chromium@512852      426.435 +- 10.2498      6      bad
chromium@512900      424.38 +- 15.1666       6      bad
chromium@512997      431.596 +- 7.25978      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.css

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

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


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

Comment 6 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    : blink_perf.css
  Metric       : LoadBootstrapBlog/LoadBootstrapBlog
  Change       : 13.05% | 80.2453333333 -> 90.7165

Revision             Result                   N
chromium@512824      80.2453 +- 0.714263      6      good
chromium@512825      90.587 +- 0.648068       6      bad       <--
chromium@512826      90.4818 +- 0.566214      6      bad
chromium@512828      90.4538 +- 0.748667      6      bad
chromium@512832      89.944 +- 0.632903       6      bad
chromium@512840      90.4093 +- 0.457536      6      bad
chromium@512855      89.7042 +- 0.779744      6      bad
chromium@512885      90.7165 +- 0.644215      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.css

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

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


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

Comment 7 by 42576172...@developer.gserviceaccount.com, Nov 4 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    : blink_perf.css
  Metric       : LoadSemanticPageExample/LoadSemanticPageExample
  Change       : 23.71% | 350.192833333 -> 433.2285

Revision             Result                  N
chromium@512803      350.193 +- 13.1957      6      good
chromium@512816      345.87 +- 12.9146       6      good
chromium@512822      348.467 +- 10.2705      6      good
chromium@512824      346.491 +- 16.7571      6      good
chromium@512825      428.28 +- 11.1461       6      bad       <--
chromium@512828      435.657 +- 14.471       6      bad
chromium@512852      434.535 +- 8.68392      6      bad
chromium@512900      426.772 +- 24.2487      6      bad
chromium@512997      433.229 +- 8.09529      6      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.css

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

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


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

Sign in to add a comment