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

Issue 755083 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.3%-95.6% regression in system_health.memory_mobile at 489897:493966

Project Member Reported by petermarshall@chromium.org, Aug 14 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 14 2017

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

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


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

android-nexus5X
android-nexus7v2
android-one
chromium-rel-mac11-pro
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 14 2017

Mergedinto: 752416
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Michael Hablich
  Commit : 7b7658d8c800e8a42d2c0b5bc9bbe63155a69a22
  Date   : Wed Aug 02 08:28:01 2017
  Subject: Version 6.2.118.1 (cherry-pick)

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_yandex
  Change       : 7.94% | 5073010.0 -> 5475856.66667

Revision                           Result                  N
chromium@489896                    5073010 +- 66853.6      6       good
chromium@490727                    4984699 +- 41254.2      14      good
chromium@491142                    5045801 +- 852261       21      good
chromium@491246                    4969769 +- 23465.6      6       good
chromium@491298                    4966172 +- 10445.6      9       good
chromium@491324                    5043539 +- 688166       14      good
chromium@491337                    5096093 +- 1029195      21      good
chromium@491344                    4967334 +- 28485.3      14      good
chromium@491346                    5067801 +- 944322       21      good
chromium@491346,v8@7b7658d8c8      5436556 +- 36209.3      9       bad       <--
chromium@491347                    5444521 +- 26244.7      14      bad
chromium@491350                    5429634 +- 63783.4      14      bad
chromium@491557                    5467020 +- 18710.0      14      bad
chromium@493218                    5475857 +- 51106.3      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.search.yandex 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/8971300324352767808


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment