New issue
Advanced search Search tips

Issue 764613 link

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



Sign in to add a comment

70.5%-389% regression in v8.browsing_mobile at 501042:501100

Project Member Reported by jgruber@chromium.org, Sep 13 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 13 2017 

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

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


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

android-webview-nexus6
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 13 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_imgur


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=browse.media.imgur v8.browsing_mobile

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

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


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

Comment 6 by 42576172...@developer.gserviceaccount.com, Sep 14 2017

Mergedinto: 764614
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : nednguyen
  Commit : aca6ca9eacf53d6d12f599ba6b9011951fde2017
  Date   : Mon Sep 11 16:56:48 2017
  Subject: Use --ignore-certificate-errors for webview

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_imgur
  Change       : 405.63% | 5.6905 -> 28.7726666667

Revision                                 Result                  N
chromium@500946                          5.6905 +- 1.20963       6      good
chromium@500994                          6.3695 +- 1.8787        6      good
chromium@501006                          6.07883 +- 1.03861      6      good
chromium@501009                          5.75483 +- 1.79189      6      good
chromium@501011                          5.79167 +- 1.03899      6      good
chromium@501011,catapult@59c0f71abc      5.77117 +- 1.63025      6      good
chromium@501011,catapult@0ed6f7d08a      5.68767 +- 1.95328      6      good
chromium@501011,catapult@aca6ca9eac      26.9763 +- 14.3387      6      bad       <--
chromium@501012                          26.4388 +- 18.4613      6      bad
chromium@501018                          24.787 +- 22.0207       6      bad
chromium@501041                          28.7727 +- 9.96767      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=browse.media.imgur v8.browsing_mobile

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

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


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

Comment 7 by 42576172...@developer.gserviceaccount.com, Sep 14 2017 


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

Suspected Commit
  Author : nednguyen
  Commit : aca6ca9eacf53d6d12f599ba6b9011951fde2017
  Date   : Mon Sep 11 16:56:48 2017
  Subject: Use --ignore-certificate-errors for webview

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_max/browse_media/browse_media_imgur
  Change       : 101.15% | 5.6135 -> 11.2916666667

Revision                                 Result                  N
chromium@500946                          5.6135 +- 0.826925      6      good
chromium@500994                          5.85617 +- 1.23085      6      good
chromium@501006                          5.78283 +- 1.11989      6      good
chromium@501009                          5.59983 +- 0.62415      6      good
chromium@501011                          5.94517 +- 1.89951      6      good
chromium@501011,catapult@59c0f71abc      5.839 +- 1.02786        6      good
chromium@501011,catapult@0ed6f7d08a      5.83367 +- 1.42248      6      good
chromium@501011,catapult@aca6ca9eac      11.0737 +- 3.43032      6      bad       <--
chromium@501012                          10.9805 +- 2.94128      6      bad
chromium@501018                          10.342 +- 1.32127       6      bad
chromium@501041                          11.2917 +- 3.7497       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=browse.media.imgur v8.browsing_mobile

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

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


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

Sign in to add a comment