New issue
Advanced search Search tips

Issue 681639 link

Starred by 0 users

Issue metadata

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



Sign in to add a comment

9% regression in system_health.memory_mobile at 442907:443061

Project Member Reported by nzolghadr@chromium.org, Jan 16 2017

Issue description

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

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


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

android-nexus9
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 16 2017

Mergedinto: 680781
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : ericrk
  Commit : 916f273d2383cfca5c75a930793f096b1b5677ca
  Date   : Wed Jan 11 22:18:33 2017
  Subject: Remove ShallowFlushCHROMIUM after resource deletion

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_social/load_social_twitter
  Change       : 7.13% | 198825301.333 -> 213002922.667

Revision             Result                     N
chromium@442906      198825301 +- 4824506       6      good
chromium@442987      200405447 +- 15699972      9      good
chromium@443006      199568043 +- 5071035       6      good
chromium@443009      197558272 +- 3515809       6      good
chromium@443010      197492736 +- 3068317       6      good
chromium@443011      216214187 +- 3764376       6      bad       <--
chromium@443015      217852587 +- 4221522       6      bad
chromium@443024      215930197 +- 4885547       6      bad
chromium@443061      213002923 +- 12059574      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=load.social.twitter system_health.memory_mobile

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

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


| 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 Tests>AutoBisect.  Thank you!

Sign in to add a comment