New issue
Advanced search Search tips

Issue 902457 link

Starred by 1 user
Status: Duplicate
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

A zero-to-nonzero to 6.1% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 604381:604528

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

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

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

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


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

Android Nexus5 Perf
Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

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

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

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/10fbf885e40000

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
thread_raster_cpu_time_per_frame: 0 → 0.1377 (+0.1377)

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

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

Comment 4 by oysteine@google.com, Nov 27

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

Sign in to add a comment