New issue
Advanced search Search tips

Issue 918613 link

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



Sign in to add a comment

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

Project Member Reported by chiniforooshan@chromium.org, Jan 2 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 2 

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

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


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, Jan 3

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

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.5237 → 0.5734 (+0.04972)

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

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

Sign in to add a comment