New issue
Advanced search Search tips

Issue 890873 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.4%-60.7% regression in rendering.mobile/avg_surface_fps at 594520:594578

Project Member Reported by tdres...@chromium.org, Oct 1

Issue description

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

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


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
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/14900ce4e40000

Defer returning resources from display compositor by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/5358dbe0785f91b2208e77853e6ff3691fc1d43e
2.115 → 2.45 (+0.335)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
 Issue 890876  has been merged into this issue.

Sign in to add a comment