New issue
Advanced search Search tips

Issue 894520 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

6%-637.1% regression in rendering.mobile/mean_frame_time_renderer_compositor at 598489:598650

Project Member Reported by majidvp@chromium.org, Oct 11

Issue description

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

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


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/10f40e32e40000

gpu: Expand oopr workaround to fallback to ES2 to all android versions. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/332d9329983d602d6bc1f4e0b64afec2307e70ba
queueing_durations: 0.2733 → 1.661 (+1.388)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: enne@chromium.org vmi...@chromium.org
Status: WontFix (was: Assigned)
This should have brought us back to the performance we had with GPU raster. I'm going to run the rendering benchmarks again now that OOP is also using ES2 and compare against GPU raster to see what the real regressions are.
Cc: majidvp@google.com
 Issue 894890  has been merged into this issue.
Cc: npm@chromium.org
 Issue 895393  has been merged into this issue.
 Issue 895269  has been merged into this issue.

Sign in to add a comment