New issue
Advanced search Search tips

Issue 897683 link

Starred by 1 user
Status: Duplicate
Merged: issue 897682
Owner: ----
Closed: Oct 22
Cc:
nzolghadr@chromium.org
hjd@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.2% regression in rendering.mobile/tasks_per_frame_total_all at 601213:601273

Project Member Reported by hjd@google.com, Oct 22 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 22 

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

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


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

android-nexus5x-perf

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

Comment 3 by hjd@google.com, Oct 22

Mergedinto: 897682
Status: Duplicate (was: Untriaged)
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Oct 22

Cc: nzolghadr@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12c2c7dae40000

Remove input metric ukm sampling by nzolghadr@chromium.org
https://chromium.googlesource.com/chromium/src/+/f509a32b60352f85ed29950b1a24752ad14ce35e
tasks_per_frame_total_all: 48.03 → 50.56 (+2.522)

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

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

Sign in to add a comment