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

Issue 886817 link

Starred by 1 user
Status: Duplicate
Merged: issue 883356
Owner:
boliu@chromium.org
Closed: Sep 21
Cc:
boliu@chromium.org
█ alexclarke@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 590450:590561

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

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

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

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


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 21

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/106b2f7b640000

aw: ReturnedResourceAvailable by boliu@chromium.org
https://chromium.googlesource.com/chromium/src/+/0d8d0e26871adce7024452945a9aec30ac18989c
0 → 2297 (+2297)

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

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

Comment 4 by boliu@chromium.org, Sep 21

Mergedinto: 883356
Status: Duplicate (was: Assigned)
►

Sign in to add a comment