New issue
Advanced search Search tips

Issue 911204 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 911591
Owner:
Closed: Dec 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 2.6% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 612639:612810

Project Member Reported by maxlg@chromium.org, Dec 3

Issue description

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

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


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
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/10c93572140000

HTTP status code 401: Login Required

Cc: masonfreed@chromium.org
Owner: masonfreed@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/116f8c1fe40000

Removing the kInlineTransform compositing reason by masonfreed@chromium.org
https://chromium.googlesource.com/chromium/src/+/f6e075c54c8bc6130d49c09ad3df6944376ccba4
thread_total_all_cpu_time_per_frame: 11.26 → 13.42 (+2.159)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Mergedinto: 911591
Status: Duplicate (was: Assigned)
Same general comments as 911591.

Sign in to add a comment