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

Issue 606877 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 606760
Owner:
Last visit > 30 days ago
Closed: May 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

18.7%-31.8% regression in blink_perf.pywebsocket at 389449:389473

Project Member Reported by pmeenan@chromium.org, Apr 26 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=606877

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


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

chromium-rel-mac-hdd
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Apr 26 2016


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@389448         293.016667  7.249681    12          good
chromium@389473         299.829412  18.875837   17          bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 606877

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.pywebsocket
Test Metric: fetch-send-text-window-async-verify/fetch-send-text-window-async-verify
Relative Change: 6.37%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/498
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014291763401644944


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

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


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@389448         290.494444  7.400117    18          good
chromium@389473         291.683333  7.801678    18          bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 606877

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.pywebsocket
Test Metric: fetch-send-text-window-async-verify/fetch-send-text-window-async-verify
Relative Change: 1.30%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/501
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014205537563487584


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

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


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@389448  205.728  12.7538  18  good
chromium@389473  200.378  12.7703  18  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 606877

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.pywebsocket
Test Metric: WebSocket-receive-window-async-verify/WebSocket-receive-window-async-verify
Relative Change: 0.61%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/503
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014197879408515536


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

| 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!
Rekicked bisect with a different range
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Apr 28 2016


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@389432  297.056  10.0166  18  good
chromium@389474  297.519  5.77214  16  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 606877

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.pywebsocket
Test Metric: fetch-send-text-window-async-verify/fetch-send-text-window-async-verify
Relative Change: 2.08%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/504
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014135728003303024


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

| 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!
Kicked off a wider bisect with 40 iterations.
Mergedinto: 606760
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Add field trial testing config for MojoChannel
Author  : rockot
Commit description:
  
R=asvitkine@chromium.org
BUG=

Review URL: https://codereview.chromium.org/1918583002

Cr-Commit-Position: refs/heads/master@{#389497}
Commit  : bf36f2d46f43eff11f56ea205615f092801b1004
Date    : Mon Apr 25 16:47:03 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@389400  289.58  10.0515  5  good
chromium@389450  299.9   4.75132  5  good
chromium@389475  296.98  2.51734  5  good
chromium@389488  301.04  7.00628  5  good
chromium@389494  303.08  6.4422   5  good
chromium@389496  299.92  6.52932  5  good
chromium@389497  394.28  11.5157  5  bad    <--
chromium@389500  399.18  44.1268  5  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 606877

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.pywebsocket
Test Metric: fetch-send-text-window-async-verify/fetch-send-text-window-async-verify
Relative Change: 37.85%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/542
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013146743619251120


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

| 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