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

Issue 887318 link

Starred by 1 user
Status: WontFix
Owner:
sunn...@chromium.org
Closed: Sep 21
Cc:
sunn...@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.1% regression in rendering.desktop at 588294:588770

Project Member Reported by alexclarke@chromium.org, Sep 20 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 20 

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

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


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

Win 7 Nvidia GPU Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 21

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/114d6537640000

cc: Finish frame early if main thread is idle regardless of redraw state by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/c13dcf77ea89896271187aa929923ed84bc57dd0
50.59 → 53.64 (+3.047)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 4 by sunn...@chromium.org, Sep 21

Status: WontFix (was: Assigned)
CL was reverted
►

Sign in to add a comment