New issue
Advanced search Search tips

Issue 845881 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: 2018-07-09
OS: ----
Pri: 3
Type: Bug-Regression



Sign in to add a comment

2.7% improvement in memory.top_10_mobile at 1526342846:1526347671

Project Member Reported by perezju@google.com, May 23 2018

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

perf-go-webview-phone
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 24 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-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_m_intl_taobao_com_group_purchase_html
  Change       : 3.20% | 17181848.5714 -> 16631668.0

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/aed427b076ba209b24b49a72ce9d7c4637984029..16cc308525e06e1bcaf8c7c7208c75419835240e


Revision                                       Result                  N
android-chrome@4426288b2b                      17181849 +- 355021      14       good
android-chrome@4426288b2b,chromium@557768      17008183 +- 269314      21       good
android-chrome@4426288b2b,chromium@557819      17192308 +- 360320      9        good
android-chrome@4426288b2b,chromium@557844      17118068 +- 223485      14       good
android-chrome@4426288b2b,chromium@557856      17012230 +- 271346      21       good
android-chrome@4426288b2b,chromium@557857      17118653 +- 351489      14       good
android-chrome@4426288b2b,chromium@557858      ---                     ---      build failure
android-chrome@4426288b2b,chromium@557859      16613675 +- 328663      14       bad
android-chrome@4426288b2b,chromium@557862      16334879 +- 354309      6        bad
android-chrome@4426288b2b,chromium@557868      16725364 +- 279298      14       bad
android-chrome@4426288b2b,chromium@558065      16671775 +- 249694      6        bad
android-chrome@dda312c828                      16631668 +- 399808      14       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=http.m.intl.taobao.com.group.purchase.html memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection
Labels: Pri-3
NextAction: 2018-07-09
Downgrading P2 issues unmodified for more than 6 months, which have no owner or component.

Sign in to add a comment