New issue
Advanced search Search tips

Issue 746252 link

Starred by 0 users
Status: Duplicate
Merged: issue 747796
Owner:
mlippautz@chromium.org
Closed: Jul 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.5%-33.2% regression in system_health.memory_desktop at 487072:487164

Project Member Reported by mlippautz@chromium.org, Jul 19 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 19 2017 

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

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


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

android-webview-nexus5X
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 20 2017

Owner: mlippautz@chromium.org

=== Auto-CCing suspected CL author mlippautz@chromium.org ===

Hi mlippautz@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 : Michael Lippautz
  Commit : 24195a6d06985906a72fa2fcf27546bcb10a4a99
  Date   : Mon Jul 17 13:04:02 2017
  Subject: [heap] Scavenger: Use LABs

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_max/browse_media/browse_media_imgur
  Change       : 23.30% | 15.583 -> 19.3711111111

Revision                           Result                   N
chromium@487076                    15.583 +- 0.994555       6      good
chromium@487113                    14.798 +- 1.59929        9      good
chromium@487132                    15.6234 +- 2.85211       9      good
chromium@487141                    15.553 +- 1.25715        6      good
chromium@487146                    15.4017 +- 2.11167       6      good
chromium@487146,v8@9a0403a679      15.5933 +- 1.27886       6      good
chromium@487146,v8@07a743df0a      15.4598 +- 1.18592       6      good
chromium@487146,v8@24195a6d06      18.9748 +- 4.08617       6      bad       <--
chromium@487147                    19.8875 +- 0.970739      6      bad
chromium@487148                    19.86 +- 0.905425        6      bad
chromium@487150                    19.3711 +- 3.54208       9      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/8973651745178977184


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

Comment 4 by 42576172...@developer.gserviceaccount.com, Jul 21 2017 

 Issue 747259  has been merged into this issue.

Comment 8 by mlippautz@chromium.org, Jul 24 2017

Cc: -mlippautz@chromium.org
While there might be an issue with LABs, I don't see how this it can affect Parse and Compilation buckets (yet). Kicked off a few more bisects.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jul 24 2017

Mergedinto: 747796
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Mythri Alle
  Commit : 51e582272983e7b49f395ccce1f3c56e1dc2d722
  Date   : Mon Jul 17 14:39:35 2017
  Subject: Enable memory metric, v8.compile category on v8.runtimestats.browse*

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : Parse:duration_avg/browse_news/browse_news_flipboard
  Change       : 18.69% | 251.327666667 -> 298.305777778

Revision             Result                  N
chromium@487029      251.328 +- 57.3935      9      good
chromium@487053      257.96 +- 10.5226       9      good
chromium@487065      245.261 +- 46.9184      6      good
chromium@487071      257.057 +- 39.3254      9      good
chromium@487074      256.744 +- 42.0453      9      good
chromium@487075      303.696 +- 10.2727      6      bad       <--
chromium@487076      298.306 +- 49.7511      9      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard v8.runtimestats.browsing_desktop

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

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


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

Comment 10 by 42576172...@developer.gserviceaccount.com, Jul 24 2017 


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

Suspected Commit
  Author : Mythri Alle
  Commit : 51e582272983e7b49f395ccce1f3c56e1dc2d722
  Date   : Mon Jul 17 14:39:35 2017
  Subject: Enable memory metric, v8.compile category on v8.runtimestats.browse*

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : Compile:duration_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 6.97% | 119.163111111 -> 127.469333333

Revision             Result                  N
chromium@487038      119.163 +- 13.95        9      good
chromium@487068      119.42 +- 3.8121        6      good
chromium@487072      119.474 +- 4.80825      6      good
chromium@487074      118.63 +- 4.16199       6      good
chromium@487075      129.154 +- 2.53194      6      bad       <--
chromium@487076      131.483 +- 8.33131      6      bad
chromium@487083      130.712 +- 2.93244      6      bad
chromium@487098      127.469 +- 4.01003      9      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook.infinite.scroll v8.runtimestats.browsing_desktop

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

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


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

Comment 11 by 42576172...@developer.gserviceaccount.com, Jul 25 2017 


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

Suspected Commit
  Author : Mythri Alle
  Commit : 51e582272983e7b49f395ccce1f3c56e1dc2d722
  Date   : Mon Jul 17 14:39:35 2017
  Subject: Enable memory metric, v8.compile category on v8.runtimestats.browse*

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Compile:duration_avg/browse_news/browse_news_cnn
  Change       : 7.87% | 3747.06322222 -> 4042.05811111

Revision             Result                  N
chromium@487037      3747.06 +- 742.625      9      good
chromium@487057      3711.63 +- 436.137      6      good
chromium@487067      3660.13 +- 257.467      6      good
chromium@487072      3531.93 +- 713.944      6      good
chromium@487074      3655.93 +- 252.351      6      good
chromium@487075      4057.43 +- 720.194      9      bad       <--
chromium@487076      4042.06 +- 522.773      9      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.cnn v8.runtimestats.browsing_mobile

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

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


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

Sign in to add a comment