New issue
Advanced search Search tips

Issue 606889 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 606760
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

45.4% regression in blink_perf.pywebsocket at 389433:389448

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=606889

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


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

Cc: keishi@chromium.org
Owner: keishi@chromium.org

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

Hi keishi@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : CrossThreadPersistentRegion will only trace objects belonging to the current GCing ThreadHeap
Author  : keishi
Commit description:
  
CrossThreadPersistentRegion will be globally shared so we need to limit the tracing to objects belonging to the current GCing ThreadHeap.

BUG= 591606 

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

Cr-Commit-Position: refs/heads/master@{#389433}
Commit  : 8cc8d1cd549bcb95653e501f6f2a4b77170d1d1a
Date    : Mon Apr 25 08:47:15 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@389432         211.46      1.627268    5           good
chromium@389433         223.62      4.985679    5           bad         <-
chromium@389434         225.78      6.355863    5           bad
chromium@389436         222.5       4.944189    5           bad
chromium@389440         220.58      7.035055    5           bad
chromium@389448         220.975     7.609533    8           bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 606889

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-arraybuffer-window-async-verify/fetch-send-arraybuffer-window-async-verify
Relative Change: 3.89%
Score: 99.0

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


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

| 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 3 by keishi@chromium.org, Apr 27 2016

r389433 was reverted in r389469 but it hasn't fixed the regression
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Apr 27 2016

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 Value  Std. Dev.   Num Values  Good?
chromium@389410         214.28      5.776418    5           good
chromium@389458         227.44      7.771937    5           good
chromium@389482         222.78      4.668726    5           good
chromium@389494         228.88      10.517462   5           good
chromium@389496         222.54      0.971082    5           good
chromium@389497         321.5       6.980688    5           bad         <-
chromium@389500         335.84      32.577646   5           bad
chromium@389506         317.22      6.8558      5           bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 606889

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-arraybuffer-window-async-verify/fetch-send-arraybuffer-window-async-verify
Relative Change: 48.04%
Score: 99.9

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


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

| 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