New issue
Advanced search Search tips

Issue 875388 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 17
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

52.6% regression in webrtc_perf_tests at 24240:24241

Project Member Reported by brandtr@chromium.org, Aug 17

Issue description

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

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


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

webrtc-linux-large-tests
Owner: sprang@chromium.org
Status: Assigned (was: Untriaged)
Looks caused by https://webrtc-review.googlesource.com/93287.

-> sprang to verify this is expected.
Status: WontFix (was: Assigned)
Some interesting results here!
Most of stats are improvements. The idea with this change was to not set a too high minimum quality as this would result in increased delays and possibly need to keyframes.

It seems like by doing this we also avoid some overshooting detection from trigering and reducing overall quality - so both min and average psnr/ssim has improved substantially, like 5dB in the simulcast screenshare case!

Few dropped frames, higher overall media bitrate. With that of course comes increased network delay in some situations, but it seems well controlled.

I'll mark this as wai.

Sign in to add a comment