New issue
Advanced search Search tips

Issue 895393 link

Starred by 1 user
Status: Duplicate
Merged: issue 894520
Owner:
khushals...@chromium.org
Closed: Oct 16
Cc:
npm@chromium.org
khushals...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

18.4%-33.8% regression in rendering.mobile/avg_surface_fps at 598489:598582

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

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

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

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


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

Android Nexus5X WebView 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 16

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/14bf0912e40000

gpu: Expand oopr workaround to fallback to ES2 to all android versions. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/332d9329983d602d6bc1f4e0b64afec2307e70ba
avg_surface_fps: 21.06 → 17.3 (-3.758)

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

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

Comment 4 by khushals...@chromium.org, Oct 16

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

Sign in to add a comment