New issue
Advanced search Search tips

Issue 901889 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 905162
Owner:
Closed: Nov 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4%-69.4% regression in rendering.mobile/avg_surface_fps at 604118:604550

Project Member Reported by tdres...@chromium.org, Nov 5

Issue description

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

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


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
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/10326cd9e40000

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: 74.96 → 100.6 (+25.65)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Mergedinto: 905162
Status: Duplicate (was: Assigned)

Sign in to add a comment