New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 764715 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.8% regression in system_health.memory_mobile at 500990:501106

Project Member Reported by mustaq@chromium.org, Sep 13 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 13 2017

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 13 2017

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

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

Hi ericrk@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 : Eric Karl
  Commit : bc1b89a7d0fd2965b10544651d3be31e77f9ff64
  Date   : Mon Sep 11 20:27:00 2017
  Subject: Revert "Use GPU Discardable in Image Decode Cache"

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/background_tools/background_tools_gmail
  Change       : 1.85% | 16433152.0 -> 16737621.3333

Revision             Result                   N
chromium@500989      16433152 +- 0.0          6      good
chromium@501019      16433152 +- 0.0          6      good
chromium@501020      16736256 +- 0.0          6      bad       <--
chromium@501021      16737621 +- 7478.24      6      bad
chromium@501023      16737621 +- 7478.24      6      bad
chromium@501027      16736256 +- 11585.2      6      bad
chromium@501034      16738987 +- 9459.31      6      bad
chromium@501048      16736256 +- 0.0          6      bad
chromium@501106      16737621 +- 7478.24      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.tools.gmail 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/8968559186676260992


For feedback, file a bug with component Speed>Bisection

Comment 4 by ericrk@chromium.org, Sep 13 2017

Status: WontFix (was: Assigned)
We had to revert this feature as it caused leaks on other platforms. Will try to re-land in the future.
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 13 2017

 Issue 764707  has been merged into this issue.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Sep 13 2017

 Issue 764707  has been merged into this issue.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Sep 15 2017

Issue 764709 has been merged into this issue.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Sep 19 2017

Cc: alexclarke@chromium.org
 Issue 766519  has been merged into this issue.

Sign in to add a comment