New issue
Advanced search Search tips

Issue 883763 link

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



Sign in to add a comment

5.6%-12.3% regression in rendering.mobile at 588435:588726

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

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

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

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


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
Project Member

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

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 17

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/146ab8e3640000

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

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

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

Comment 6 by sunn...@chromium.org, Sep 20

Status: WontFix (was: Assigned)
CL was reverted, and graphs have recovered.
►

Sign in to add a comment