New issue
Advanced search Search tips

Issue 902755 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.2%-40.9% regression in rendering.mobile/thread_raster_cpu_time_per_frame at 600933:601033

Project Member Reported by lanwei@chromium.org, Nov 7

Issue description

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

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


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

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

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: khushals...@chromium.org
Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14674183e40000

gpu: Fix raster implementation error for no flush result available query by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/da82bcce69bf5384435976a1945c9cb3270c5abb
thread_raster_cpu_time_per_frame: 5.549 → 7.919 (+2.37)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Status: WontFix (was: Assigned)
The regression is countering an improvement from a previous change that introduced an error this change fixed.

Sign in to add a comment