New issue
Advanced search Search tips

Issue 671532 link

Starred by 1 user
Status: Duplicate
Owner:
u...@chromium.org
Closed: Dec 2016
Cc:
leszeks@chromium.org
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.6%-62.6% regression in v8.browsing_mobile_ignition at 435915:436165

Project Member Reported by leszeks@chromium.org, Dec 6 2016 
Bisecting
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 6 2016 


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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@436034  12074943  7991696  27  good
chromium@436036  12578895  6950651  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 671532

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes v8.browsing_mobile_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_max/browse_news/browse_news_nytimes
Relative Change: 4.17%

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


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

| 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, Dec 6 2016 


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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@436034  12057678  7602967  27  good
chromium@436085  12086841  7389094  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 671532

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes v8.browsing_mobile_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:code_and_metadata_size_max/browse_news/browse_news_nytimes
Relative Change: 0.24%

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


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

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

Comment 6 by leszeks@chromium.org, Dec 21 2016

Status: WontFix (was: Assigned)
Looks like whatever this was is now gone.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Mar 23 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile_ignition
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_max/browse_news/browse_news_nytimes

Revision             Result                   N
chromium@436034      12034701 +- 7647098      21      good
chromium@436036      11915517 +- 6136806      21      bad

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.news.nytimes v8.browsing_mobile_ignition

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

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


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

Comment 10 by 42576172...@developer.gserviceaccount.com, Mar 25 2017

Cc: u...@chromium.org
Owner: u...@chromium.org

=== Auto-CCing suspected CL author ulan@chromium.org ===

Hi ulan@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : ulan
  Commit : aea4f1a704829fcb3fc3584b9d9948deeb5bcaa5
  Date   : Fri Dec 02 16:34:12 2016
  Subject: [heap] Use RAIL mode for initial heap sizing

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile_ignition
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:code_and_metadata_size_max/browse_social/browse_social_facebook
  Change       : 30.66% | 2608020.0 -> 3407583.33333

Revision                           Result                  N
chromium@435968                    2608020 +- 221335       6      good
chromium@435993                    2648791 +- 296087       6      good
chromium@435995                    2614343 +- 269250       6      good
chromium@435996                    2582824 +- 204564       6      good
chromium@435996,v8@e7a51fff24      2549313 +- 76460.3      6      good
chromium@435996,v8@aea4f1a704      3460976 +- 98924.8      6      bad       <--
chromium@435997                    3434849 +- 159814       6      bad
chromium@436000                    3446715 +- 73955.8      6      bad
chromium@436006                    3363156 +- 205903       6      bad
chromium@436018                    3314394 +- 232812       6      bad
chromium@436067                    3453526 +- 132772       6      bad
chromium@436165                    3407583 +- 133522       6      bad

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 v8.browsing_mobile_ignition

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

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


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

Comment 11 by leszeks@chromium.org, Mar 27 2017

Mergedinto: 671118
Status: Duplicate (was: WontFix)
Sorry for the spam Ulan, don't know why the bisect kicked off.
►

Sign in to add a comment