New issue
Advanced search Search tips

Issue 900884 link

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



Sign in to add a comment

10% regression in rendering.mobile/tasks_per_frame_total_all at 603905:603968

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 1 

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

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


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, Nov 1

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

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
tasks_per_frame_total_all: 22.19 → 24.19 (+1.993)

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

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

Comment 4 by oysteine@chromium.org, Nov 2

Mergedinto: 888558
Status: Duplicate (was: Assigned)
►

Sign in to add a comment