New issue
Advanced search Search tips

Issue 764707 link

Starred by 1 user
Status: Duplicate
Merged: issue 764715
Owner: ----
Closed: Sep 2017
Cc:
mustaq@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.7%-799.3% regression in system_health.memory_mobile at 500905:501053

Project Member Reported by mustaq@chromium.org, Sep 13 2017 
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=764707

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


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

android-nexus5X
android-one
Project Member

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

Mergedinto: 764715
Status: Duplicate (was: Untriaged)

=== 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_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/https_m_facebook_com_rihanna
  Change       : 833.28% | 63824.0 -> 595654.0

Revision             Result              N
chromium@500935      63824.0 +- 0.0      6      good
chromium@500994      63824.0 +- 0.0      6      good
chromium@501009      63824.0 +- 0.0      6      good
chromium@501017      63824.0 +- 0.0      6      good
chromium@501019      63824.0 +- 0.0      6      good
chromium@501020      595654 +- 0.0       6      bad       <--
chromium@501021      595654 +- 0.0       6      bad
chromium@501024      595654 +- 0.0       6      bad
chromium@501053      595654 +- 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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests 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/8968561274382859024


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

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


=== 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_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/https_m_facebook_com_rihanna
  Change       : 833.28% | 63824.0 -> 595654.0

Revision             Result              N
chromium@500935      63824.0 +- 0.0      6      good
chromium@500994      63824.0 +- 0.0      6      good
chromium@501009      63824.0 +- 0.0      6      good
chromium@501017      63824.0 +- 0.0      6      good
chromium@501019      63824.0 +- 0.0      6      good
chromium@501020      595654 +- 0.0       6      bad       <--
chromium@501021      595654 +- 0.0       6      bad
chromium@501024      595654 +- 0.0       6      bad
chromium@501053      595654 +- 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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests 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/8968561337832407600


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment