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

Issue 664967 link

Starred by 1 user
Status: WontFix
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Closed: Feb 2017
Cc:
jgruber@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 669608
issue 672529


Sign in to add a comment

9.9% regression in v8.browsing_mobile at 431604:431640

Project Member Reported by jgruber@chromium.org, Nov 14 2016 
See the link to graphs below.

Comment 1 by jgruber@chromium.org, Nov 14 2016 

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 14 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@431603  141.585  509.062  40  good
chromium@431640  145.77   506.833  40  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 664967

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_mobile
Test Metric: v8-gc-scavenger_sum/v8-gc-scavenger_sum
Relative Change: None

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


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

| 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 rbyers@chromium.org, Nov 18 2016

Labels: Performance
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Nov 19 2016 


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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@429359  N/A   N/A      0  good
chromium@431723  N/A   N/A      0  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 664967

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_mobile
Test Metric: v8-gc-scavenger_sum/browse_social
Relative Change: None

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


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

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


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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@429420  N/A   N/A      0  good
chromium@431695  N/A   N/A      0  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 664967

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_mobile
Test Metric: v8-gc-scavenger_sum/browse_social
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4356
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995647913703470448


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

| 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 9 by jgruber@chromium.org, Nov 21 2016

Owner: hpayer@chromium.org
Speculatively assigning to hpayer for 

a9e6bbb [heap] Reland concurrent store buffer processing. by hpayer ยท 10 days ago

For some reason bisects fail even though the regression is clear on browse_social benchmarks.

Comment 10 by jgruber@chromium.org, Nov 21 2016

Cc: jgruber@chromium.org
 Issue 665867  has been merged into this issue.

Comment 11 by jgruber@chromium.org, Nov 21 2016 

Actually, forget the speculative CL revision above; I did not notice the 'Next' link on the revision list, and the revision range is quite a bit larger. Keeping this assigned to hpayer@ as the current memory sheriff.
Project Member

Comment 14 by 42576172...@developer.gserviceaccount.com, Dec 10 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@429359  94.0257  362.179  42  good
chromium@431723  143.21   59.0139  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 664967

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_mobile
Test Metric: v8-gc-scavenger_sum/browse_social
Relative Change: 52.31%

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


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

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


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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@429420  166.725  287.894  8  good
chromium@431695  335.017  17.6996  4  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 664967

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.browsing_mobile
Test Metric: v8-gc-scavenger_sum/browse_social
Relative Change: 100.94%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4432
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993752658261693792


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

| 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 16 by simonhatch@chromium.org, Dec 12 2016

Blockedon: 672529
 crbug.com/672529  for 1 hour timeout.

Comment 17 by simonhatch@chromium.org, Dec 15 2016 

FYI: This isn't a real regression, the twitter page was disabled:
https://codereview.chromium.org/2489423004

Re-enabled at a later date:
https://codereview.chromium.org/2522593007

Comment 18 by simonhatch@chromium.org, Dec 15 2016

Blockedon: 669608
Project Member

Comment 20 by 42576172...@developer.gserviceaccount.com, Jan 13 2017 


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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-scavenger_sum/browse_social

Revision             Result                  N
chromium@429420      165.846 +- 85.8939      13      good
chromium@431695      327.516 +- 73.9246      14      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 v8.browsing_mobile

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

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


| 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 21 by hpayer@chromium.org, Feb 24 2017

Status: WontFix (was: Assigned)
Project Member

Comment 24 by 42576172...@developer.gserviceaccount.com, Apr 11 2017 


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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-scavenger_sum/browse_social

Revision             Result                  N
chromium@429420      165.846 +- 85.8939      13      good
chromium@431695      327.516 +- 73.9246      14      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 v8.browsing_mobile

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

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


| 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 27 by 42576172...@developer.gserviceaccount.com, Apr 11 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-scavenger_sum/browse_social


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

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

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


| 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 28 by 42576172...@developer.gserviceaccount.com, Apr 11 2017 


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-scavenger_sum/browse_social

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/c11bed35d016206740715e7b990ef870ba62a5a7..bb1c8b9d3e4acb60fb489f878963e2ccbb936b61


Revision             Result                  N
chromium@429420      166.725 +- 287.894      8      good
chromium@431695      335.017 +- 17.6996      4      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 v8.browsing_mobile

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

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


| 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 29 by 42576172...@developer.gserviceaccount.com, Apr 11 2017 


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-scavenger_sum/v8-gc-scavenger_sum

Revision             Result                 N
chromium@431603      217.64 +- 200.438      20      good
chromium@431640      225.81 +- 160.921      19      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 v8.browsing_mobile

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

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


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

Sign in to add a comment