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

Issue 781708 link

Starred by 1 user
Status: WontFix
Owner:
█ marpan@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Cc:
jianj@chromium.org
ilnik@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.9% improvement in webrtc_perf_tests at 20542:20542

Project Member Reported by ilnik@chromium.org, Nov 6 2017 
Chromium roll containing libvpx update reduced encode time and psnr for VP9 2SL config.

Marco, is the encode time change expected? What about a PSNR?

PSNR may also be explained by increased number of frames, including the hard ones, but it's unlikely because we got only two extra frames in the test. They couldn't cause 0.5dB PSNR change.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 6 2017 

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

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


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

webrtc-win-large-tests

Comment 2 by marpan@chromium.org, Nov 6 2017

Cc: jianj@chromium.org
Status: WontFix (was: Assigned)
There were some changes in that roll that could cause decrease in encode time, and maybe small decrease in PSNR, depending on clip and bitrate.
Not sure why the screenshare_vp9_2sl test on windows has ~0.4-0.5dB drop, could be partly related to increased number of frames. Since its only that particular test and only on windows, we'll mark this as won't fix.
►

Sign in to add a comment