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

Issue 596820 link

Starred by 0 users
Status: Duplicate
Merged: issue 596823
Owner:
█ alexclarke@chromium.org
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

110.9% regression in smoothness.top_25_smooth at 382313:382346

Project Member Reported by alexclarke@chromium.org, Mar 22 2016 
Looks like a clear regression.

Comment 1 by alexclarke@chromium.org, Mar 22 2016 

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

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


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

chromium-rel-mac-retina
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Mar 22 2016 


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


===== SUSPECTED CL(s) =====
Subject : Re-land enabling wheel gestures on all platforms.
Author  : dtapuska
Commit description:
  
Changes since last attempt in https://codereview.chromium.org/1724783002/

MacOSX implementation has landed in
https://codereview.chromium.org/1749343004/

The Android perf regression has been eliminated because the default
wheel transaction is set to 0. The perf regression was because the
wheel transaction time was added to the total time of the test.

Attention perf sherrifs; a minor perf regression is expected in
this change. 8-10% when locally on my Nexus 5; this minor regression is
anticipated because of the new code paths.

BUG= 568183 

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

Cr-Commit-Position: refs/heads/master@{#382345}
Commit  : ca4feba9a31e10d1baab5813650c192e06cfd643
Date    : Mon Mar 21 19:00:47 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@382312         29.749158   0.303405    5           good
chromium@382330         29.71925    0.391741    5           good
chromium@382338         29.790567   0.102363    5           good
chromium@382342         29.86565    0.264411    5           good
chromium@382344         30.14925    0.231072    5           good
chromium@382345         63.379957   9.130833    5           bad
chromium@382346         56.797676   11.533109   5           bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 596820

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/mean_input_event_latency
Relative Change: 90.92%
Score: 99.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1220
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017497034556717872


| 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 label Cr-Tests-AutoBisect.  Thank you!
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 22 2016 


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


===== SUSPECTED CL(s) =====
Subject : Re-land enabling wheel gestures on all platforms.
Author  : dtapuska
Commit description:
  
Changes since last attempt in https://codereview.chromium.org/1724783002/

MacOSX implementation has landed in
https://codereview.chromium.org/1749343004/

The Android perf regression has been eliminated because the default
wheel transaction is set to 0. The perf regression was because the
wheel transaction time was added to the total time of the test.

Attention perf sherrifs; a minor perf regression is expected in
this change. 8-10% when locally on my Nexus 5; this minor regression is
anticipated because of the new code paths.

BUG= 568183 

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

Cr-Commit-Position: refs/heads/master@{#382345}
Commit  : ca4feba9a31e10d1baab5813650c192e06cfd643
Date    : Mon Mar 21 19:00:47 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@382312         29.931067   0.302819    5           good
chromium@382330         29.902525   0.230701    5           good
chromium@382338         29.713483   0.191252    5           good
chromium@382342         29.692175   0.138568    5           good
chromium@382344         29.949708   0.302561    5           good
chromium@382345         58.777538   7.448667    5           bad
chromium@382346         56.310468   8.895057    5           bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 596820

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/mean_input_event_latency
Relative Change: 88.13%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1221
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017497015437423984


| 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 label Cr-Tests-AutoBisect.  Thank you!
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Mar 22 2016 


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


===== SUSPECTED CL(s) =====
Subject : Re-land enabling wheel gestures on all platforms.
Author  : dtapuska
Commit description:
  
Changes since last attempt in https://codereview.chromium.org/1724783002/

MacOSX implementation has landed in
https://codereview.chromium.org/1749343004/

The Android perf regression has been eliminated because the default
wheel transaction is set to 0. The perf regression was because the
wheel transaction time was added to the total time of the test.

Attention perf sherrifs; a minor perf regression is expected in
this change. 8-10% when locally on my Nexus 5; this minor regression is
anticipated because of the new code paths.

BUG= 568183 

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

Cr-Commit-Position: refs/heads/master@{#382345}
Commit  : ca4feba9a31e10d1baab5813650c192e06cfd643
Date    : Mon Mar 21 19:00:47 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@382312         30.193208   0.540048    5           good
chromium@382330         29.8392     0.350989    5           good
chromium@382338         29.928933   0.169323    5           good
chromium@382342         30.077633   0.198166    5           good
chromium@382344         29.708567   0.183641    5           good
chromium@382345         60.449356   6.570511    5           bad
chromium@382346         56.679357   6.757363    5           bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 596820

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/mean_input_event_latency
Relative Change: 87.72%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1224
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017491544983240096


| 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 label Cr-Tests-AutoBisect.  Thank you!
►

Sign in to add a comment