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

Issue 814255 link

Starred by 1 user
Status: Duplicate
Merged: issue 813875
Owner:
chrishtr@chromium.org
Closed: Feb 2018
Cc:
█ alexclarke@chromium.org
skobes@chromium.org
chrishtr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

35.3%-48.3% improvement in smoothness.key_silk_cases at 537107:537200

Project Member Reported by alexclarke@chromium.org, Feb 21 2018 
Suspiciously large improvement, did something break?
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 21 2018 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=c870dca34c449a80fa90451858270e7faa50907b4524e61657258937cfc73093


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 23 2018

Cc: chrishtr@chromium.org skobes@chromium.org
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://chromeperf.appspot.com/job/13bc83fb840000

[RLS] Skip compositing input step if a scroll can be applied directly. by chrishtr@chromium.org
https://chromium.googlesource.com/chromium/src/+/32419f4422bf130d9c52331a0c7dafba9337cc99

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by chrishtr@chromium.org, Feb 23 2018

Mergedinto: 813875
Status: Duplicate (was: Assigned)

Comment 5 by chrishtr@google.com, Feb 24 2018 

My CL caused a progression in metrics, but that was expected.
►

Sign in to add a comment