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

Issue 755084 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

1.1%-1.9% regression in system_health.memory_mobile at 489897:493317

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=755084

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


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

android-nexus7v2
android-one
Project Member

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

Mergedinto: 752867
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Jakob Kummerow
  Commit : 05e862f78398d8bbeacc7f9e19bbb41c408e709b
  Date   : Fri Aug 04 01:27:42 2017
  Subject: Cache StoreIC-Transition handlers

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_chrome/load_chrome_blank
  Change       : 1.42% | 1817480.0 -> 1843200.0

Revision                           Result              N
chromium@489896                    1817480 +- 0.0      6      good
chromium@491557                    1816536 +- 0.0      6      good
chromium@491973                    1817396 +- 0.0      6      good
chromium@492077                    1817420 +- 0.0      6      good
chromium@492129                    1817420 +- 0.0      6      good
chromium@492155                    1817420 +- 0.0      6      good
chromium@492159                    1817420 +- 0.0      6      good
chromium@492161                    1817420 +- 0.0      6      good
chromium@492161,v8@5614747680      1817420 +- 0.0      6      good
chromium@492161,v8@2fd5e70a03      1817864 +- 0.0      6      good
chromium@492161,v8@9735d7f109      1817864 +- 0.0      6      good
chromium@492161,v8@0caf1d2029      1815764 +- 0.0      6      good
chromium@492161,v8@05e862f783      1843276 +- 0.0      6      bad       <--
chromium@492162                    1844676 +- 0.0      6      bad
chromium@492168                    1844676 +- 0.0      6      bad
chromium@492181                    1844676 +- 0.0      6      bad
chromium@492388                    1835976 +- 0.0      6      bad
chromium@493218                    1843200 +- 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 --story-filter=load.chrome.blank 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/8971300259397476832


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment