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

Issue 861714 link

Starred by 1 user
Status: WontFix
Owner:
sprang@chromium.org
Closed: Jul 9
Cc:
█ philipel@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

24.4% regression in webrtc_perf_tests at 23832:23836

Project Member Reported by philipel@chromium.org, Jul 9
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 9 

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

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


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

webrtc-win-large-tests

Comment 2 by sprang@chromium.org, Jul 9

Status: WontFix (was: Assigned)
This only affects the experiment group with alternative temporal layer layouts.

Looks like encoder is dropping more frames but maintaining a higher bitrate. Delays up by 15ms or so.
Average PSNR is up 1.5dB!

It's weird that we're encoding this at so high framerate. I think we should change the test to be at 30fps since that will be much more common.

In any case I'll close this bug for now.
►

Sign in to add a comment