New issue
Advanced search Search tips

Issue 670761 link

Starred by 0 users
Status: WontFix
Owner:
u...@chromium.org
Closed: Jul 2017
Cc:
qyears...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.7%-22.8% regression in system_health.memory_mobile at 431506:434580

Project Member Reported by qyears...@chromium.org, Dec 2 2016 
See the link to graphs below.
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 3 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@433555  40003486  121014437  135  good
chromium@434543  42048938  39852522   15   bad

Bisect job ran on: linux_perf_bisect
Bug ID: 670761

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max
Relative Change: 5.11%

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


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

| 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@433555  39173194  118730317  135  good
chromium@434580  39765130  49822810   20   bad

Bisect job ran on: linux_perf_bisect
Bug ID: 670761

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max
Relative Change: 1.51%

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


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

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

Blockedon: 669608
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Dec 7 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@433555  41960819  51681215  25  good
chromium@434580  42103164  52080220  25  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 670761

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max
Relative Change: 0.34%

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


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

| 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 10 by pmeenan@chromium.org, Dec 13 2016 

Kicked a bisect from the second alerted graph (avg object size) which looks to be a clean test and regression: https://chromeperf.appspot.com/buildbucket_job_status/8993378837913515568
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Dec 13 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@433555  31341623  32525711  30  good
chromium@434580  32331321  25746381  20  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 670761

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg
Relative Change: 3.16%

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


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

| 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, Jan 13 2017 


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.infinite_scroll_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg

Revision             Result                   N
chromium@433555      31315895 +- 3562254      21      good
chromium@434580      30765730 +- 0.0          1       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2

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

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


| 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 14 by qyears...@chromium.org, Apr 4 2017

Blockedon: -669608
Project Member

Comment 16 by 42576172...@developer.gserviceaccount.com, Apr 5 2017 


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.infinite_scroll_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max

Revision             Result                   N
chromium@433555      40690964 +- 8791050      21      good
chromium@434580      40202297 +- 5885872      17      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2

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

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


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


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.infinite_scroll_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max

Revision             Result                   N
chromium@433555      40633188 +- 6295795      21      good
chromium@434543      39968495 +- 8164889      19      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll_tbmv2

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

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


| 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 22 by mustaq@chromium.org, Jul 10 2017 

Most of these bugs re v8.infinite_scroll_tbmv2 should be handled through  Issue 724262  .

Comment 23 by u...@chromium.org, Jul 11 2017

Owner: u...@chromium.org

Comment 24 by u...@chromium.org, Jul 11 2017

Status: WontFix (was: Untriaged)
Bisect bot cannot reproduce the regression.
►

Sign in to add a comment