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

Issue 868798 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 30
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.1%-33.3% regression in webrtc_perf_tests at 23979:23980

Project Member Reported by asapersson@chromium.org, Jul 30

Issue description

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

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


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

webrtc-win-large-tests
Owner: marpan@chromium.org
Cc: jianj@chromium.org
The small increase in media bitrate for screenshare test can be expected from the roll, as we've been making changes to screen-content mode.

There are 2 positive gains (min_pnsr and dropped frame) for the svc_medium test. The other reported regressions are memory usage and these are positive gains (reduced memory usage). 

Don't really see how the libvpx roll improved the memory usage metric. Jerome do you have any idea? Suggest we mark this as won't fix, since it only effects windows and they seem to be positive gains.


Status: WontFix (was: Untriaged)
The improvement of memory usage is due to the fix:
https://chromium.googlesource.com/webm/libvpx.git/+/a01896354d3845bce18899cb31d1871e985c8483

Close this issue for now.

Sign in to add a comment