New issue
Advanced search Search tips

Issue 877392 link

Starred by 1 user
Status: WontFix
Owner:
altimin@chromium.org
Closed: Sep 10
Cc:
altimin@chromium.org
petermarshall@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

39.1% regression in v8.browsing_desktop at 584964:584973

Project Member Reported by petermarshall@chromium.org, Aug 24 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 24 

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

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


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

linux-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 24 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14efae51640000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 24

Cc: altimin@chromium.org
Owner: altimin@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16beb2d9640000

[scheduler] Enable prioritising compositing after input on waterfall by altimin@chromium.org
https://chromium.googlesource.com/chromium/src/+/e38ad59a34b356c0315e13da8829ba7ef78bfe6b
6.315 → 7.819 (+1.504)

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

Comment 6 by altimin@chromium.org, Sep 10

Status: WontFix (was: Assigned)
This is a side-effect of us making scrolling faster (which is desired).
►

Sign in to add a comment