New issue
Advanced search Search tips

Issue 917230 link

Starred by 2 users
Status: Assigned
Owner: ----
Cc:
kouhei@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

24.4% regression in rendering.mobile/thread_raster_cpu_time_per_frame at 607617:608487

Project Member Reported by kouhei@google.com, Dec 21 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 21 

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

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


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

android-nexus5x-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 21

Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12ba3616140000

Roll src/clank bb6faab8400f..09e33be0a917 (1 commits) by chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com
https://chrome-internal.googlesource.com/chrome/src-internal/+/680d3bc1592df262ec1ad01ae7540e7fe00781be
thread_raster_cpu_time_per_frame: 0.39 → 0.4607 (+0.07074)

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

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

Sign in to add a comment