New issue
Advanced search Search tips

Issue 898889 link

Starred by 1 user

Issue metadata

Status: Closed
Owner: ----
Closed: Nov 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5%-18.5% regression in rendering.mobile/tasks_per_frame_total_all at 601213:601297

Project Member Reported by maxlg@chromium.org, Oct 25

Issue description

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15c4539ae40000
Status: Closed (was: Untriaged)
Closed until a difference is found.
Cc: nzolghadr@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1386a497e40000

Remove input metric ukm sampling by nzolghadr@chromium.org
https://chromium.googlesource.com/chromium/src/+/f509a32b60352f85ed29950b1a24752ad14ce35e
tasks_per_frame_total_all: 56.24 → 60.86 (+4.625)

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

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

Sign in to add a comment