New issue
Advanced search Search tips

Issue 881911 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 880421
Owner:
Closed: Sep 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.8%-20.4% regression in media.mobile at 588274:588284

Project Member Reported by tguilbert@chromium.org, Sep 7

Issue description

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

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


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

android-nexus5x-perf

media.mobile - Benchmark documentation link:
  None
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/111f4c55640000
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/1677aeb5640000

Revert "Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers" by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/6eb9eee331affe92c52a2926f57422bcbf40fa43
1.281e+07 → 1.458e+07 (+1.769e+06)

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

Benchmark documentation link:
  None
Mergedinto: 880421
Status: Duplicate (was: Assigned)

Sign in to add a comment