New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 887289 link

Starred by 1 user
Status: Duplicate
Merged: issue 887312
Owner:
khushals...@chromium.org
Closed: Sep 20
Cc:
█ alexclarke@chromium.org
khushals...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.1%-10.3% regression in rendering.mobile at 592113:592304

Project Member Reported by alexclarke@chromium.org, Sep 20 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 20 

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 20

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/134e50a7640000

gpu: Expand oopr workaround to fallback to ES2 to all android versions. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/2b62fe723102af55ae3c3508d013655647af440b
50.64 → 54.3 (+3.656)

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

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

Comment 4 by khushals...@chromium.org, Sep 20

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

Sign in to add a comment