[remoting] Poor video performance over WebRTC relay connections |
||
Issue description[Tracked internally as b/79163660] With relay P2P connections, we are seeing some very laggy and stuttery video performance. Same problem is not seen with the Chrome app. It's mostly visible on YouTube videos, or any motion taking up a lot of screen space. Initially, the performance is fine, but after a minute or two it seems to degrade. Problem only seems to affect relayed connections - direct/stun connections seem fine.
,
Jul 16
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c2f2b188908cf27a464152ed36f502888a10756c commit c2f2b188908cf27a464152ed36f502888a10756c Author: Lambros Lambrou <lambroslambrou@chromium.org> Date: Mon Jul 16 21:27:43 2018 [remoting WebRTC] Cap bitrate over relay connections This applies a rate-limit on sending data over a relayed connection, to avoid lots of packet loss because the b/w estimator does not work well with the relay server implementation. The cap level was determined based on internal discussions with the TURN server team. We may decide to change it in future. For example, the max-bitrate of the connection could be expressed by the TURN service in the ICE config response. Bug: 857287 Change-Id: I5de96749ebd8f647d211738f01bd039edbc94241 Reviewed-on: https://chromium-review.googlesource.com/1125411 Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org> Reviewed-by: Joe Downing <joedow@chromium.org> Cr-Commit-Position: refs/heads/master@{#575427} [modify] https://crrev.com/c2f2b188908cf27a464152ed36f502888a10756c/remoting/protocol/webrtc_transport.cc
,
Sep 21
Marking as Fixed. The biggest performance problems have been addressed, but there are still some server-side (TURN) improvements that are being worked on. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Jul 11