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

Issue 886646 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 21
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9%-18.1% regression in rendering.desktop at 591207:591256

Project Member Reported by alexclarke@chromium.org, Sep 19

Issue description

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

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


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

linux-perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/101dd7c0e40000
Cc: sunn...@chromium.org
Owner: sunn...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14570e24e40000

Revert "cc: Finish frame early if main thread is idle regardless of redraw state" by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/2bbe289cc8e1ba48e6aac024521bafeb489f3ea0
95.25 → 77.13 (-18.11)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Status: WontFix (was: Assigned)
Due to a revert

Sign in to add a comment