New issue
Advanced search Search tips

Issue 816511 link

Starred by 1 user
Status: Fixed
Owner:
ccameron@chromium.org
Closed: Apr 2018
Cc:
sdy@chromium.org
tdres...@chromium.org
ccameron@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.1% regression in battor.steady_state at 537577:537618

Project Member Reported by tdres...@chromium.org, Feb 26 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-mac11-pro
Project Member

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

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

mac: Don't pause for frames with no frame sink by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/5a89487894c5c141e32bd716d72ce4e0f63800d4

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

Comment 4 by charliea@chromium.org, Apr 3 2018 

Hey Chris,

It looks like the bisect found that that your CL, https://chromium.googlesource.com/chromium/src/+/5a89487894c5c141e32bd716d72ce4e0f63800d4, caused a ~5% regression in CPU time.

Was this expected? If so, we should mark this as fixed. If not, we should probably revert it and investigate.

Comment 5 by ccameron@chromium.org, Apr 3 2018

Status: Fixed (was: Assigned)
Yes, this a return to previous behavior.

Comment 6 by charliea@chromium.org, May 23 2018 

 Issue 816508  has been merged into this issue.
►

Sign in to add a comment