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

Issue 905489 link

Starred by 1 user
Status: Duplicate
Merged: issue 905495
Owner:
█ hubbe@chromium.org
Last visit > 30 days ago
Closed: Nov 15
Cc:
piman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

38.3% regression in media.desktop at 607401:607477

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

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

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

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


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

linux-perf

media.desktop - Benchmark documentation link:
  None
Project Member

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

Cc: piman@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/137b7337e40000

Use SharedImageInterface for one-copy staging buffers by piman@chromium.org
https://chromium.googlesource.com/chromium/src/+/9058f7866e74b92eeef1c30780522fba0740d2f3
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 9.553e+06 → 1.309e+07 (+3.539e+06)

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

Benchmark documentation link:
  None

Comment 4 by hubbe@chromium.org, Nov 15

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

Sign in to add a comment