New issue
Advanced search Search tips

Issue 883765 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

3.3%-58.5% regression in rendering.mobile at 588619:588744

Project Member Reported by npm@chromium.org, Sep 13

Issue description

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
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/172c4875640000

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

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Status: WontFix (was: Assigned)
CL was reverted, and graphs have recovered.

Sign in to add a comment