New issue
Advanced search Search tips

Issue 893805 link

Starred by 1 user
Status: Duplicate
Merged: issue 893772
Owner:
sunn...@chromium.org
Closed: Oct 10
Cc:
sunn...@chromium.org
m...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-26.3% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 593294:596520

Project Member Reported by m...@chromium.org, Oct 9 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 9 

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

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


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
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 10

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

Defer returning resources from display compositor by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/5358dbe0785f91b2208e77853e6ff3691fc1d43e
thread_raster_cpu_time_per_frame: 0.2525 → 0.3241 (+0.07157)

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

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

Comment 4 by m...@chromium.org, Oct 10

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

Sign in to add a comment