New issue
Advanced search Search tips

Issue 893783 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 893772
Owner:
Closed: Oct 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.5%-25.8% regression in blink_perf.layout at 593294:596519

Project Member Reported by m...@chromium.org, Oct 9

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=893783

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


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

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

blink_perf.layout - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
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/14dbcdace40000

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

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Mergedinto: 893772
Status: Duplicate (was: Assigned)

Sign in to add a comment