New issue
Advanced search Search tips

Issue 859163 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jun 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.5%-45.1% regression in system_health.webview_startup at 1527777591:1530148789

Project Member Reported by majidvp@chromium.org, Jun 29 2018

Issue description

The largest regression seems to in in facebook. BTW there are small improvements in multiple other pages.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 29 2018

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

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


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

health-plan-webview-low-end-phone
perf-go-webview-phone
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 30 2018

Mergedinto: 853659
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Yutaka Hirano
  Commit : 0f9ea91ea461cb3d432a250ede3b9e3ddf6b522f
  Date   : Thu Jun 14 05:46:46 2018
  Subject: Enable RendererSideResourceScheduler

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:cc:effective_size_avg/load_news/load_news_cnn
  Change       : 37.59% | 3487144.0 -> 4797864.0

Revision                                       Result                 N
android-chrome@d79bf90511                      3487144 +- 0.0         6       good
android-chrome@e90c9c80c5                      3487144 +- 0.0         14      good
android-chrome@cd7b16c40c                      3786737 +- 632879      21      good
android-chrome@cd7b16c40c,chromium@567145      3711839 +- 571164      14      good
android-chrome@cd7b16c40c,chromium@567157      3711839 +- 571164      14      good
android-chrome@cd7b16c40c,chromium@567158      3599491 +- 420366      14      good
android-chrome@cd7b16c40c,chromium@567159      4610618 +- 737370      14      bad       <--
android-chrome@cd7b16c40c,chromium@567165      4385923 +- 807748      14      bad
android-chrome@306d8fee9b                      4610618 +- 737370      14      bad
android-chrome@6b97f109ea                      5060008 +- 0.0         6       bad
android-chrome@2fe77d170f                      4273576 +- 861493      6       bad
android-chrome@56a8706b95                      4797864 +- 642119      6       bad
android-chrome@31cb7d3927                      4161229 +- 807748      14      bad
android-chrome@a5a5234c1c                      4498271 +- 782099      14      bad
android-chrome@12fcaddca5                      4885245 +- 524288      9       bad
android-chrome@8062d9e01c                      4797864 +- 642119      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.news.cnn 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/8942357139237692016


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment