New issue
Advanced search Search tips

Issue 790975 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 789441
Owner: ----
Closed: Dec 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

25.4% regression in v8.browsing_mobile at 519232:519255

Project Member Reported by jgruber@chromium.org, Dec 1 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=790975

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


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

android-webview-nexus5X

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-scavenger_sum/browse_news/browse_news_washingtonpost

Revision             Result                  N
chromium@519231      53.3064 +- 10.9111      21      good
chromium@519255      52.5811 +- 12.1315      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=browse.news.washingtonpost 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/8961415467434078848


For feedback, file a bug with component Speed>Bisection
Mergedinto: 789441
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Tsuyoshi Horo
  Commit : e9cdaa227686d4e995569173d451cab0767ac48f
  Date   : Mon Nov 27 09:57:08 2017
  Subject: Add PWAFullCodeCache to fieldtrial_testing_config.json

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-scavenger_sum/browse_news/browse_news_washingtonpost
  Change       : 25.21% | 52.2866666667 -> 65.4661666667

Revision             Result                  N
chromium@519231      52.2867 +- 4.7465       6      good
chromium@519247      52.1025 +- 5.81912      6      good
chromium@519255      54.4448 +- 5.33228      6      good
chromium@519259      53.5402 +- 5.11857      6      good
chromium@519260      53.6617 +- 8.39396      6      good
chromium@519261      66.744 +- 9.0244        6      bad       <--
chromium@519263      68.7575 +- 5.39922      6      bad
chromium@519294      65.4662 +- 12.4298      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.news.washingtonpost 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/8960860608329653232


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment