New issue
Advanced search Search tips

Issue 901913 link

Starred by 1 user
Status: Fixed
Owner:
oysteine@chromium.org
Closed: Nov 30
Cc:
oysteine@chromium.org
tdres...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.6%-19.8% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 603899:604489

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

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

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

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


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

Android Nexus5 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@chromium.org
Owner: oysteine@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16eea4e1e40000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
thread_total_all_cpu_time_per_frame: 29.82 → 32.75 (+2.931)

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

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

Comment 4 by oysteine@chromium.org, Nov 30

Status: Fixed (was: Assigned)
http://crrev.com/612360
►

Sign in to add a comment