New issue
Advanced search Search tips

Issue 784960 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

3.4%-13.2% regression in system_health.memory_mobile at 515943:515977

Project Member Reported by tdres...@chromium.org, Nov 14 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-webview-nexus6
Project Member

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

Mergedinto: 785007
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Michael Starzinger
  Commit : 23883b85f21a2c61515cb57064b19901ae666884
  Date   : Thu Nov 09 09:31:15 2017
  Subject: [deoptimizer] Turn deopt entries into immovable Code objects.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_tools/load_tools_stackoverflow
  Change       : 12.72% | 3647448.66667 -> 4111538.66667

Revision                           Result                  N
chromium@515942                    3647449 +- 120500       6      good
chromium@515951                    3669139 +- 60936.3      6      good
chromium@515951,v8@1ea3fd2e13      3442826 +- 37434.1      6      good
chromium@515951,v8@6aa3349afb      3424258 +- 85791.3      6      good
chromium@515951,v8@a9c908eb40      3445333 +- 89470.6      6      good
chromium@515951,v8@23883b85f2      3882065 +- 58174.3      6      bad       <--
chromium@515951,v8@b9c9932202      3894263 +- 72310.6      6      bad
chromium@515951,v8@d1193e3c6c      3892374 +- 69548.1      6      bad
chromium@515951,v8@2328e4d196      3888920 +- 67065.4      6      bad
chromium@515952                    4100385 +- 79503.4      6      bad
chromium@515953                    4099188 +- 89362.8      6      bad
chromium@515954                    4108554 +- 95714.0      6      bad
chromium@515956                    4111066 +- 79335.1      6      bad
chromium@515960                    4128908 +- 49950.7      6      bad
chromium@515977                    4111539 +- 69060.6      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.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 --story-filter=load.tools.stackoverflow system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment