New issue
Advanced search Search tips

Issue 697911 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

2975%-5175% regression in system_health.memory_mobile at 452799:452857

Project Member Reported by sullivan@chromium.org, Mar 2 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=697911

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxOuauQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxIWztAsM


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

android-webview-nexus5X
android-webview-nexus6
Mergedinto: 697910
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : yhirano
  Commit : 865407349e3755b33d6db5642501f88c8fb7784d
  Date   : Fri Feb 24 14:43:30 2017
  Subject: Do not reuse a loading resource associated with another fetcher

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/load_social/load_social_tumblr
  Change       : 5175.00% | 131072.0 -> 6914048.0

Revision             Result              N
chromium@452819      131072 +- 0.0       6      good
chromium@452822      131072 +- 0.0       6      good
chromium@452823      6914048 +- 0.0      6      bad       <--
chromium@452824      6914048 +- 0.0      6      bad
chromium@452828      6914048 +- 0.0      6      bad
chromium@452838      6914048 +- 0.0      6      bad
chromium@452857      6914048 +- 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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.tumblr system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8986217083397226480

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5640288971784192


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Labels: Performance-Memory
Labels: -Performance-Memory

Sign in to add a comment