New issue
Advanced search Search tips

Issue 839755 link

Starred by 2 users
Status: Duplicate
Merged: issue 838456
Owner:
wangxianzhu@chromium.org
Closed: Jun 2018
Cc:
wangxianzhu@chromium.org
hjd@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2577.1% regression in system_health.memory_mobile at 1524802457:1525317877

Project Member Reported by hjd@google.com, May 4 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 4 2018 

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

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


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

perf-go-phone-1024
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 4 2018 


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_search/load_search_taobao
  Change       : 2385.32% | 177899.0 -> 4421355.0

Suspected Commit Range
  12 commits in range
  https://chromium.googlesource.com/chromium/src/+log/e80ef296fb0b839978fc7eef23fba567ba1d8e7e..b1d8c49e3c969c8b99cedc9df5ef8ff0af3ba755


Revision                                       Result              N
android-chrome@069a782c20                      177899 +- 0.0       6        good
android-chrome@f4ca9a80b7                      177899 +- 0.0       6        good
android-chrome@5e7f0484c1                      177899 +- 0.0       6        good
android-chrome@5e7f0484c1,chromium@554232      177899 +- 0.0       6        good
android-chrome@5e7f0484c1,chromium@554266      177899 +- 0.0       6        good
android-chrome@5e7f0484c1,chromium@554276      177899 +- 0.0       6        good
android-chrome@5e7f0484c1,chromium@554277      ---                 ---      build failure
---                                            ---                 ---      too many build failures to list
android-chrome@5e7f0484c1,chromium@554287      ---                 ---      build failure
android-chrome@5e7f0484c1,chromium@554288      4421355 +- 0.0      6        bad
android-chrome@5e7f0484c1,chromium@554305      4421355 +- 0.0      6        bad
android-chrome@452ccfa0f7                      4421355 +- 0.0      6        bad
android-chrome@0f6680b944                      4421355 +- 0.0      6        bad
android-chrome@13da4d3a3f                      4421355 +- 0.0      6        bad
android-chrome@bf9c45de3e                      4421355 +- 0.0      6        bad
android-chrome@87acbefda8                      4421355 +- 0.0      6        bad
android-chrome@061a8220c9                      4421355 +- 0.0      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.taobao 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/8947466689492450064


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

Comment 6 by 42576172...@developer.gserviceaccount.com, Jun 2 2018

Cc: wangxianzhu@chromium.org
Owner: wangxianzhu@chromium.org
Status: Assigned (was: Untriaged)

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

Hi wangxianzhu@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 : Xianzhu Wang
  Commit : 976fc1e074a07d78fc4ccb3ab2a9fbd20fd9ce69
  Date   : Fri Apr 27 03:05:06 2018
  Subject: [SPv175+] Don't create a new chunk with different id and the same properties.

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/load_search/load_search_taobao
  Change       : 2286.36% | 185474.333333 -> 4426086.16667

Revision                                       Result                  N
android-chrome@7efa2ba1f1                      185474 +- 8812.33       6      good
android-chrome@972eebff76                      191163 +- 8812.33       6      good
android-chrome@4e4cf7775f                      185474 +- 8812.33       6      good
android-chrome@5e7f0484c1                      188319 +- 9346.89       6      good
android-chrome@5e7f0484c1,chromium@554232      185474 +- 8812.33       6      good
android-chrome@5e7f0484c1,chromium@554266      188319 +- 9346.89       6      good
android-chrome@5e7f0484c1,chromium@554276      188319 +- 9346.89       6      good
android-chrome@5e7f0484c1,chromium@554279      185474 +- 8812.33       6      good
android-chrome@5e7f0484c1,chromium@554280      182630 +- 6966.76       6      good
android-chrome@5e7f0484c1,chromium@554281      4431775 +- 9346.89      6      bad       <--
android-chrome@5e7f0484c1,chromium@554282      4426086 +- 6966.76      6      bad
android-chrome@5e7f0484c1,chromium@554288      4423242 +- 0.0          6      bad
android-chrome@5e7f0484c1,chromium@554305      4428930 +- 8812.33      6      bad
android-chrome@452ccfa0f7                      4428930 +- 8812.33      6      bad
android-chrome@0f6680b944                      4428930 +- 8812.33      6      bad
android-chrome@efed3974e3                      4426086 +- 6966.76      6      bad
android-chrome@d3db009934                      4434619 +- 8812.33      6      bad
android-chrome@061a8220c9                      4426086 +- 6966.76      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.search.taobao 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/8944889902051788512


For feedback, file a bug with component Speed>Bisection

Comment 7 by wangxianzhu@chromium.org, Jun 2 2018

Mergedinto: 838456
Status: Duplicate (was: Assigned)
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jun 2 2018

Status: Assigned (was: Duplicate)

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

Hi wangxianzhu@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 : Xianzhu Wang
  Commit : 976fc1e074a07d78fc4ccb3ab2a9fbd20fd9ce69
  Date   : Fri Apr 27 03:05:06 2018
  Subject: [SPv175+] Don't create a new chunk with different id and the same properties.

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_search/load_search_taobao
  Change       : 2385.32% | 177899.0 -> 4421355.0

Revision                                       Result              N
android-chrome@069a782c20                      177899 +- 0.0       6      good
android-chrome@f4ca9a80b7                      177899 +- 0.0       6      good
android-chrome@5e7f0484c1                      177899 +- 0.0       6      good
android-chrome@5e7f0484c1,chromium@554232      177899 +- 0.0       6      good
android-chrome@5e7f0484c1,chromium@554266      177899 +- 0.0       6      good
android-chrome@5e7f0484c1,chromium@554276      177899 +- 0.0       6      good
android-chrome@5e7f0484c1,chromium@554279      177899 +- 0.0       6      good
android-chrome@5e7f0484c1,chromium@554280      177899 +- 0.0       6      good
android-chrome@5e7f0484c1,chromium@554281      4421355 +- 0.0      6      bad       <--
android-chrome@5e7f0484c1,chromium@554282      4421355 +- 0.0      6      bad
android-chrome@5e7f0484c1,chromium@554288      4421355 +- 0.0      6      bad
android-chrome@5e7f0484c1,chromium@554305      4421355 +- 0.0      6      bad
android-chrome@452ccfa0f7                      4421355 +- 0.0      6      bad
android-chrome@d3953c5ec8                      4421355 +- 0.0      6      bad
android-chrome@13da4d3a3f                      4421355 +- 0.0      6      bad
android-chrome@bf9c45de3e                      4421355 +- 0.0      6      bad
android-chrome@87acbefda8                      4421355 +- 0.0      6      bad
android-chrome@061a8220c9                      4421355 +- 0.0      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.taobao 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/8944889897338502064


For feedback, file a bug with component Speed>Bisection

Comment 9 by wangxianzhu@chromium.org, Jun 2 2018

Status: Duplicate (was: Assigned)
►

Sign in to add a comment