New issue
Advanced search Search tips

Issue 902891 link

Starred by 1 user
Status: Duplicate
Merged: issue 904996
Owner:
ericrk@chromium.org
Closed: Nov 13
Cc:
ericrk@chromium.org
jrumm...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.8% regression in media.mobile at 604118:604166

Project Member Reported by jrumm...@chromium.org, Nov 7 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 7 

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

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


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

Android Nexus5 Perf

media.mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 8

Cc: ericrk@chromium.org
Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14fb2663e40000

EnableGpuRasterizationViewportRestriction bot config by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/924edd7aee62613bf0d3f51b4c4d00e63f5c104e
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 7.971e+06 → 7.811e+06 (-1.605e+05)

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

Benchmark documentation link:
  None

Comment 4 by ericrk@chromium.org, Nov 13

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

Sign in to add a comment