New issue
Advanced search Search tips

Issue 883820 link

Starred by 1 user
Status: Duplicate
Merged: issue 883470
Owner:
boliu@chromium.org
Closed: Sep 14
Cc:
npm@chromium.org
boliu@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-155.7% regression in rendering.mobile at 589878:590519

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=883820

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


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 

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

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

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/153b48cb640000

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

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

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

Comment 6 by boliu@chromium.org, Sep 14

Mergedinto: 883470
Status: Duplicate (was: Assigned)
tasks per frame going up slightly is expected.
►

Sign in to add a comment