New issue
Advanced search Search tips

Issue 884304 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.7% regression in rendering.mobile at 590872:590893

Project Member Reported by npm@chromium.org, Sep 14

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=884304

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


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

Android Nexus6 WebView Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: danakj@chromium.org
Owner: danakj@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1096229d640000

Comment and clean up code for marking layers to PushPropertiesTo. by danakj@chromium.org
https://chromium.googlesource.com/chromium/src/+/956d1c82d6e8263fecbd7d2240774a7363aea2c4
0.3116 → 0.3342 (+0.02261)

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

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

Sign in to add a comment