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

Issue 806239 link

Starred by 1 user
Status: Started
Owner:
m...@chromium.org
Cc:
█ s...@chromium.org
m...@chromium.org
█ sandv@chromium.org
piman@chromium.org
chfremer@chromium.org
primiano@chromium.org
█ x...@chromium.org
mfo...@chromium.org
powerb@chromium.org
Components:
EstimatedDays: ----
NextAction: 2018-06-04
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 768335
issue 771767


Sign in to add a comment

Switching to new VIZ-based tab capture impl caused a 17.9%-48.4% regression in performance_browser_tests at 531733:531830

Project Member Reported by primiano@chromium.org, Jan 26 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 26 2018 

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

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


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

chromium-rel-mac11-air
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 26 2018

Cc: x...@chromium.org chfremer@chromium.org m...@chromium.org piman@chromium.org
Owner: m...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17c78e12840000

Rewrite WebContentsVideoCaptureDevice, to use new VIZ-based capture impl
By miu@chromium.org · Thu Jan 25 02:23:58 2018
chromium @ 77e19b91361effda2f4eb9f278d9e038aca58d7c

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

Comment 4 by m...@chromium.org, Jan 26 2018

Blockedon: 771767 768335
Status: Started (was: Assigned)
This was expected. We just switched over to a completely new implementation. Time to start the optimization work...

Comment 5 by m...@chromium.org, Jan 26 2018 

Note that performance improved a lot on other bots, such as chromium-rel-mac11-pro.

Comment 6 by m...@chromium.org, Jan 26 2018

Summary: Switching to new VIZ-based tab capture impl caused a 17.9%-48.4% regression in performance_browser_tests at 531733:531830 (was: 17.9%-48.4% regression in performance_browser_tests at 531733:531830)

Comment 7 by m...@chromium.org, Feb 1 2018

Components: Internals>Media>Capture

Comment 8 by m...@chromium.org, Feb 7 2018

Components: Internals>Media>ScreenCapture

Comment 9 by m...@chromium.org, Feb 7 2018

Components: -Internals>Media>Capture

Comment 10 by m...@chromium.org, May 15 2018

Cc: s...@chromium.org sandv@chromium.org
 Issue 806827  has been merged into this issue.

Comment 11 by m...@chromium.org, May 15 2018

NextAction: 2018-06-04
Wrapping up a project soon, will turn my attention fully to tab capture performance issues in the beginning of June.

Comment 12 by monor...@bugs.chromium.org, Jun 4 2018 

The NextAction date has arrived: 2018-06-04
►

Sign in to add a comment