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

Issue 741734 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

1.1%-7.9% regression in system_health.memory_mobile at 476613:485108

Project Member Reported by pmeenan@chromium.org, Jul 12 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 12 2017

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

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


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

android-nexus5
android-nexus7v2
android-one
Project Member

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

Mergedinto: 740469
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Dan Elphick
  Commit : 67fac36a35318d03fe141887898821e42dfaecb4
  Date   : Fri Jul 07 08:57:32 2017
  Subject: Increase priority of compositor TQ in NONE Usecase

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_media/load_media_soundcloud
  Change       : 4.41% | 34648.0 -> 36174.6666667

Revision             Result                  N
chromium@484860      34648.0 +- 0.0          14      good
chromium@484862      34648.0 +- 0.0          9       good
chromium@484863      36480.0 +- 3886.26      9       bad       <--
chromium@484864      36938.0 +- 2508.57      6       bad
chromium@484868      36938.0 +- 2508.57      6       bad
chromium@484876      36480.0 +- 3173.12      6       bad
chromium@484892      37396.0 +- 0.0          6       bad
chromium@484924      36174.7 +- 4096.48      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.soundcloud 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/8974256287989614688


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment