New issue
Advanced search Search tips

Issue 880421 link

Starred by 3 users
Status: WontFix
Owner:
sunn...@chromium.org
Closed: Sep 20
Cc:
npm@chromium.org
maxlg@chromium.org
ericrk@chromium.org
tguilbert@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

33.5%-49.6% regression in media.mobile at 588274:588276

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

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

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

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


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

android-nexus5x-perf

media.mobile - Benchmark documentation link:
  None
Project Member

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

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/174cbb6d640000

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

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

Comment 4 by ericrk@chromium.org, Sep 5

Owner: sunn...@chromium.org
This should resolve if we can find a safe way to re-land the CL I reverted. Over to sunnyps@ who is working on this CL.

Comment 5 by ericrk@chromium.org, Sep 5

Cc: maxlg@chromium.org
 Issue 880392  has been merged into this issue.

Comment 6 by ericrk@chromium.org, Sep 8 

 Issue 881911  has been merged into this issue.

Comment 7 by ericrk@chromium.org, Sep 18

Cc: npm@chromium.org
 Issue 883752  has been merged into this issue.

Comment 8 by sunn...@chromium.org, Sep 20

Status: WontFix (was: Assigned)
The original CL had a bug which caused no queries to be created, and staging buffers to be reused aggressively and incorrectly.  Re-landing the CL did not recover the graphs, but the improvement was due to a bug so WontFix.
►

Sign in to add a comment