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

Issue 887282 link

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



Sign in to add a comment

100%-1986.3% regression in rendering.mobile at 589783:590526

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

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

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

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


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

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/122b2f37640000

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

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)
This commit has generated probably 10+ perf bugs, and none of them are real.. The "not real" part is hard to avoid, but is it possible to not generate 10+ bugs for the same commit? :/
►

Sign in to add a comment