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

Issue 596821 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 596823
Owner:
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

68.6% regression in smoothness.top_25_smooth at 382313:382346

Project Member Reported by alexclarke@chromium.org, Mar 22 2016

Issue description

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

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


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

chromium-rel-mac10
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         30.132092   0.205752    5           good
chromium@382330         30.071225   0.292607    5           good
chromium@382338         29.990483   0.190076    5           good
chromium@382342         30.209867   0.128442    5           good
chromium@382344         30.103958   0.361892    5           good
chromium@382345         54.427505   8.779703    5           bad
chromium@382346         50.699221   10.115376   5           bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 596821

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: 68.26%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2055
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017496642879116064


| 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         30.209292   0.250424    5           good
chromium@382330         30.151867   0.1945      5           good
chromium@382338         30.317458   0.382648    5           good
chromium@382342         30.363325   0.227728    5           good
chromium@382344         30.322292   0.114036    5           good
chromium@382345         49.135586   4.896141    5           bad
chromium@382346         49.397762   4.705563    5           bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 596821

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: 63.52%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2056
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017496629319576896


| 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