New issue
Advanced search Search tips

Issue 909032 link

Starred by 2 users
Status: Assigned
Owner:
m...@chromium.org
Cc:
m...@chromium.org
mfo...@chromium.org
powerb@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Switching to GLScaler caused a 0%-27.8% regression in performance_browser_tests at 611023:611039

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

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

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

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


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

Google Chrome Win
linux-perf

Comment 3 by m...@chromium.org, Nov 27

Components: Internals>Media>ScreenCapture
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Nov 28

Cc: m...@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/176d5be0140000

GLRendererCopier: Replace use of GLHelper with GLScaler/GLI420Converter. by miu@chromium.org
https://chromium.googlesource.com/chromium/src/+/82751409267d5f4bfc718aebb728ae42f04e2ba6
CastV2Performance_gpu_30fps_bad_autothrottling: 2.522 → 3.494 (+0.9717)

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

Sign in to add a comment