New issue
Advanced search Search tips

Issue 883821 link

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



Sign in to add a comment

1.1%-14.9% regression in rendering.mobile at 590441:590526

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
mac-10_13_laptop_high_end-perf

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

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

Comment 3 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/11614973640000

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

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

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

Comment 4 by boliu@chromium.org, Sep 14

Cc: -boliu@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
The desktop one can't be my CL. My CL is only built into android webview.

Comment 5 by npm@chromium.org, Sep 14

Owner: boliu@chromium.org
Status: Assigned (was: Untriaged)
Summary: 1.1%-14.9% regression in rendering.mobile at 590441:590526 (was: 1.1%-14.9% regression in rendering.desktop at 590441:590526)
I incorrectly put two rendering.desktop graph into the same bug as the rendering.mobile one. But the bisect is using a rendering.mobile metric.

Comment 6 by npm@chromium.org, Sep 14 

Oh forgot to say, I've split out the rendering.desktop ones into a separate bug.

Comment 7 by boliu@chromium.org, Sep 14

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

Sign in to add a comment