New issue
Advanced search Search tips

Issue 729234 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.8%-94.4% regression in system_health.memory_mobile at 475904:476128

Project Member Reported by m...@chromium.org, Jun 2 2017

Issue description

See the link to graphs below.
 

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_facebook


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=browse.social.facebook system_health.memory_mobile

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

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


| 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!
Mergedinto: 728796
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : khushalsagar
  Commit : 4e1be6ae8914f0eeed1df004b74a467bcb93241b
  Date   : Wed May 31 21:45:49 2017
  Subject: cc: Enable perf testing for checker-imaging.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_facebook
  Change       : 92.98% | 76178221.3333 -> 147008952.0

Revision             Result                     N
chromium@475951      76178221 +- 6190653        6      good
chromium@476035      75831688 +- 6250830        6      good
chromium@476038      78151141 +- 17316201       6      good
chromium@476040      76239341 +- 19082285       6      good
chromium@476041      142259151 +- 23278698      6      bad       <--
chromium@476046      135083345 +- 34655413      6      bad
chromium@476056      141592193 +- 22830401      6      bad
chromium@476077      138729957 +- 32302549      6      bad
chromium@476119      147008952 +- 2737035       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=browse.social.facebook system_health.memory_mobile

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

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


| 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!

Sign in to add a comment