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

Issue 883470 link

Starred by 2 users
Status: WontFix
Owner:
boliu@chromium.org
Closed: Sep 13
Cc:
npm@chromium.org
boliu@chromium.org
█ ushesh@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 1.4% regression in rendering.mobile at 589783:590526

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

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

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

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

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

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

aw: ReturnedResourceAvailable by boliu@chromium.org
https://chromium.googlesource.com/chromium/src/+/0d8d0e26871adce7024452945a9aec30ac18989c
No values → 0.06224

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

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

Comment 4 by boliu@chromium.org, Sep 13

Status: WontFix (was: Assigned)
Tasks per frame going up is expected

Comment 5 by boliu@chromium.org, Sep 14

Cc: npm@chromium.org
 Issue 883820  has been merged into this issue.
►

Sign in to add a comment