New issue
Advanced search Search tips

Issue 844124 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 844112
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.1% regression in memory.top_10_mobile at 1526338717:1526349908

Project Member Reported by chiniforooshan@chromium.org, May 17 2018

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

perf-go-phone-1024
Project Member

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

Mergedinto: 844112
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : yiyix
  Commit : 6a4ede3e8b19101ba5b1735e0a2178b9541a21a3
  Date   : Mon May 14 10:38:30 2018
  Subject: Fix Regression: Black patch is seen while opening new page

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 3.34% | 6193945.77778 -> 6401021.33333

Revision                                       Result                  N
android-chrome@4426288b2b                      6193946 +- 88249.0      9       good
android-chrome@4426288b2b,chromium@558065      6164364 +- 7961.19      9       good
android-chrome@4426288b2b,chromium@558164      6222650 +- 152288       14      good
android-chrome@4426288b2b,chromium@558213      6172328 +- 6730.41      6       good
android-chrome@4426288b2b,chromium@558238      6198042 +- 89593.3      9       good
android-chrome@4426288b2b,chromium@558250      6207827 +- 104120       6       good
android-chrome@4426288b2b,chromium@558252      6200317 +- 90367.6      9       good
android-chrome@4426288b2b,chromium@558253      6419681 +- 19369.0      9       bad       <--
android-chrome@4426288b2b,chromium@558256      6370074 +- 112766       9       bad
android-chrome@4426288b2b,chromium@558262      6404662 +- 86545.3      9       bad
android-chrome@dda312c828                      6401021 +- 86720.2      9       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=http.en.m.wikipedia.org.wiki.Science 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/8946255453009959952


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment