New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 903178 link

Starred by 1 user
Status: Duplicate
Owner:
chiniforooshan@chromium.org
Closed: Nov 8
Cc:
chiniforooshan@chromium.org
█ alexclarke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 604976:605021

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

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

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

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


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

Android Nexus5X WebView Perf

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

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

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

Telemetry: remove old cpu_per_frame metrics by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/af5198be3516b3e7e5f54e9cdf6dc2882e1e4100
thread_total_all_cpu_time_per_frame: 0 → No values

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

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

Sign in to add a comment