New issue
Advanced search Search tips

Issue 902846 link

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



Sign in to add a comment

9.1%-42.7% regression in rendering.mobile/tasks_per_frame_total_all at 604426:604499

Project Member Reported by lanwei@chromium.org, Nov 7 
See the link to graphs below.
Project Member

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

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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 7

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

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
tasks_per_frame_total_all: 25.39 → 36.26 (+10.87)

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

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

Comment 4 by oysteine@google.com, Nov 27

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

Sign in to add a comment