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

Issue 636278 link

Starred by 1 user
Status: Duplicate
Merged: issue 636368
Owner:
rmcilroy@chromium.org
Closed: Aug 2016
Cc:
█ hpayer@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

33.4%-166.3% regression in v8.infinite_scroll-ignition_tbmv2 at 410689:410768

Project Member Reported by rmcilroy@chromium.org, Aug 10 2016 
See the link to graphs below.

Comment 1 by rmcilroy@chromium.org, Aug 10 2016 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtuXEpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtof2pQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtrHjuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtqPbugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtt75vQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1rvivgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtpXapwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtoTDsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtoTXqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtsDQqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgttGCsgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtu6-sgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgttzHvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1v-6vwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtvvfsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgttHmqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtryMsgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgttHxugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1rvivgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1v_LqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtpWwqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtt7jogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtuOApwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgttqkugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtvyJqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtuPyrwkM


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-nexus9
android-one
chromium-rel-mac-retina
chromium-rel-mac10
chromium-rel-mac11
linux-release

Comment 3 by rmcilroy@chromium.org, Aug 10 2016

Cc: hpayer@chromium.org
Adding Hannes since it looks like it might be a GC regression.
Project Member

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


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410734  92.8518  11.2666  5  good
chromium@410735  175.385  15.5963  5  bad
chromium@410736  154.205  15.1891  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2
Test Metric: v8-gc-total_max/v8-gc-total_max
Relative Change: 66.08%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1510
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004728310514661168


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

| 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 6 by 42576172...@developer.gserviceaccount.com, Aug 10 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410734  92.8518  11.2666  5  good
chromium@410735  175.385  15.5963  5  bad
chromium@410736  154.205  15.1891  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2
Test Metric: v8-gc-total_max/v8-gc-total_max
Relative Change: 66.08%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1510
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004728310514661168


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

| 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 9 by 42576172...@developer.gserviceaccount.com, Aug 10 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410716  48.1165  2.19762  5  good
chromium@410729  47.6395  2.22769  5  good
chromium@410732  47.9606  2.00859  5  good
chromium@410734  47.2571  1.34328  5  good
chromium@410735  87.3973  5.372    5  bad
chromium@410741  82.8696  3.43885  5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.top_25_smooth
Test Metric: v8_gc_total_outside_idle/v8_gc_total_outside_idle
Relative Change: 72.23%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/823
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004697610407542880


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

| 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 10 by 42576172...@developer.gserviceaccount.com, Aug 10 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@410726  54.4818  1.11021   5  good
chromium@410731  55.5643  2.44858   5  good
chromium@410733  54.8372  0.624405  4  good
chromium@410734  55.987   4.28311   5  good
chromium@410735  88.7475  7.95919   5  bad
chromium@410743  83.9232  4.25688   5  bad
chromium@410759  84.6631  11.5092   5  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.top_25_smooth
Test Metric: v8_gc_total/v8_gc_total
Relative Change: 55.40%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6637
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004697265603188480


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

| 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 13 by 42576172...@developer.gserviceaccount.com, Aug 10 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410716  48.1165  2.19762  5  good
chromium@410729  47.6395  2.22769  5  good
chromium@410732  47.9606  2.00859  5  good
chromium@410734  47.2571  1.34328  5  good
chromium@410735  87.3973  5.372    5  bad
chromium@410741  82.8696  3.43885  5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.top_25_smooth
Test Metric: v8_gc_total_outside_idle/v8_gc_total_outside_idle
Relative Change: 72.23%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/823
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004697610407542880


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

| 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 14 by 42576172...@developer.gserviceaccount.com, Aug 10 2016 


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@410726  54.4818  1.11021   5  good
chromium@410731  55.5643  2.44858   5  good
chromium@410733  54.8372  0.624405  4  good
chromium@410734  55.987   4.28311   5  good
chromium@410735  88.7475  7.95919   5  bad
chromium@410743  83.9232  4.25688   5  bad
chromium@410759  84.6631  11.5092   5  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.top_25_smooth
Test Metric: v8_gc_total/v8_gc_total
Relative Change: 55.40%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6637
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004697265603188480


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

| 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 18 by 42576172...@developer.gserviceaccount.com, Aug 11 2016

Mergedinto: 636368
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : [heap] Enforce finalization of marking at heap limit when optimizing for memory usage.
Author  : hpayer
Commit description:
  
BUG= chromium:634900 

Review-Url: https://codereview.chromium.org/2225363002
Cr-Commit-Position: refs/heads/master@{#38495}
Commit  : a7b7d691064f00feaa37946416e65c76d6b9926e
Date    : Tue Aug 09 13:09:14 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev   N  Good?
chromium@410726                56.5069  0.994507  5  good
chromium@410731                58.0992  2.99679   5  good
chromium@410733                59.1279  2.14547   5  good
chromium@410734                57.0716  1.95977   5  good
chromium@410734,v8@9b6d753170  56.2564  2.7461    5  good
chromium@410734,v8@2f6b26ed45  57.9911  2.63519   5  good
chromium@410734,v8@c403ab7f57  59.3599  4.60497   5  good
chromium@410734,v8@a7b7d69106  86.5293  3.13249   5  bad    <--
chromium@410735                90.4373  6.44153   5  bad
chromium@410743                92.9545  5.71389   5  bad
chromium@410759                87.3697  7.7775    5  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.top_25_smooth
Test Metric: v8_gc_total/v8_gc_total
Relative Change: 54.62%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6639
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004697265603188480


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

| 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 19 by 42576172...@developer.gserviceaccount.com, Aug 11 2016 


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


===== SUSPECTED CL(s) =====
Subject : [heap] Enforce finalization of marking at heap limit when optimizing for memory usage.
Author  : hpayer
Commit description:
  
BUG= chromium:634900 

Review-Url: https://codereview.chromium.org/2225363002
Cr-Commit-Position: refs/heads/master@{#38495}
Commit  : a7b7d691064f00feaa37946416e65c76d6b9926e
Date    : Tue Aug 09 13:09:14 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev   N  Good?
chromium@410734                54.8108  0.980111  5  good
chromium@410734,v8@9b6d753170  57.2452  2.01108   5  good
chromium@410734,v8@2f6b26ed45  54.9224  2.3532    5  good
chromium@410734,v8@c403ab7f57  55.5006  1.75569   5  good
chromium@410734,v8@a7b7d69106  113.865  4.80254   5  bad    <--
chromium@410735                115.736  9.81731   5  bad
chromium@410736                116.533  13.8895   5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.key_mobile_sites_smooth
Test Metric: v8_gc_total_outside_idle/v8_gc_total_outside_idle
Relative Change: 112.61%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2008
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004728310514661168


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

| 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 20 by 42576172...@developer.gserviceaccount.com, Aug 12 2016 


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


===== SUSPECTED CL(s) =====
Subject : [heap] Enforce finalization of marking at heap limit when optimizing for memory usage.
Author  : hpayer
Commit description:
  
BUG= chromium:634900 

Review-Url: https://codereview.chromium.org/2225363002
Cr-Commit-Position: refs/heads/master@{#38495}
Commit  : a7b7d691064f00feaa37946416e65c76d6b9926e
Date    : Tue Aug 09 13:09:14 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@410734                56.7743  1.51994  5  good
chromium@410734,v8@9b6d753170  54.7482  2.92855  5  good
chromium@410734,v8@2f6b26ed45  56.4911  2.04806  5  good
chromium@410734,v8@c403ab7f57  54.8849  2.95248  5  good
chromium@410734,v8@a7b7d69106  115.22   5.40211  5  bad    <--
chromium@410735                113.27   8.95575  5  bad
chromium@410736                117.221  8.71192  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 636278

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests v8.key_mobile_sites_smooth
Test Metric: v8_gc_total_outside_idle/v8_gc_total_outside_idle
Relative Change: 106.47%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2009
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004697610407542880


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

| 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