New issue
Advanced search Search tips

Issue 902739 link

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



Sign in to add a comment

A zero-to-nonzero to 2.8% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 605673:605768

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=902739

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


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

Android Nexus5X WebView 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: 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/11403155e40000

Telemetry: finally move rendering to TBMv2 by chiniforooshan@chromium.org
https://chromium.googlesource.com/chromium/src/+/05af02c8afe6a0fdc3d5e32ff88632fa15f5c567
tasks_per_frame_total_all: 0 → No values

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

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

Comment 4 by chiniforooshan@chromium.org, Nov 7

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

Sign in to add a comment