New issue
Advanced search Search tips

Issue 638010 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 638006
Owner:
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

56.6% regression in memory.blink_memory_mobile at 411591:411597

Project Member Reported by bashi@chromium.org, Aug 15 2016

Issue description

See the link to graphs below.
 

Comment 1 by bashi@chromium.org, Aug 15 2016

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

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


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

android-nexus5X
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Aug 16 2016

Mergedinto: 638006
Status: Duplicate (was: Assigned)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Fix wrong state of IsolateInBackgroundNotification and IsolateInForegroundNotification.
Author  : hpayer
Commit description:
  
BUG= chromium:636368 , chromium:635965 , chromium:634900 

Review-Url: https://codereview.chromium.org/2245483004
Cr-Commit-Position: refs/heads/master@{#38598}
Commit  : b992a8e1899091e3c180a050c1a63fa1e29886d5
Date    : Fri Aug 12 08:13:56 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev  N   Good?
chromium@411590                15620510  569570   12  good
chromium@411592                15501456  278414   5   good
chromium@411592,v8@64658b6c28  15929954  965242   8   good
chromium@411592,v8@e6e32315cc  15291870  602693   5   good
chromium@411592,v8@b992a8e189  16604510  419721   8   bad    <--
chromium@411593                17314671  1496292  5   bad
chromium@411594                17403880  1421814  5   bad
chromium@411597                16985756  1280354  8   bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 638010

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.blink_memory_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:peak_size_avg/memory:chrome:renderer_processes:reported_by_chrome:peak_size_avg
Relative Change: 9.61%
Score: 80.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/519
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004219747314758992


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5342773721432064

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 16 2016


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Fix wrong state of IsolateInBackgroundNotification and IsolateInForegroundNotification.
Author  : hpayer
Commit description:
  
BUG= chromium:636368 , chromium:635965 , chromium:634900 

Review-Url: https://codereview.chromium.org/2245483004
Cr-Commit-Position: refs/heads/master@{#38598}
Commit  : b992a8e1899091e3c180a050c1a63fa1e29886d5
Date    : Fri Aug 12 08:13:56 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev  N  Good?
chromium@411590                15667873  345890   8  good
chromium@411592                15527265  384099   8  good
chromium@411592,v8@64658b6c28  15533112  428751   8  good
chromium@411592,v8@e6e32315cc  15687260  1371400  8  good
chromium@411592,v8@b992a8e189  16328322  432435   8  bad    <--
chromium@411593                16946207  1329865  8  bad
chromium@411594                16591739  404445   5  bad
chromium@411597                17122535  358895   5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 638010

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.blink_memory_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:peak_size_avg/memory:chrome:renderer_processes:reported_by_chrome:peak_size_avg
Relative Change: 9.95%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/520
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004219734356607728


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5826836668350464

| 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