New issue
Advanced search Search tips

Issue 857287 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 21
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

[remoting] Poor video performance over WebRTC relay connections

Project Member Reported by lambroslambrou@chromium.org, Jun 28 2018

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.

 
Project Member

Comment 1 by bugdroid1@chromium.org, Jul 11

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/32d3a2f9447417d82e5d03a27d345f74052e76c4

commit 32d3a2f9447417d82e5d03a27d345f74052e76c4
Author: Lambros Lambrou <lambroslambrou@chromium.org>
Date: Wed Jul 11 17:51:09 2018

[remoting] Detect if WebRTC connection is relayed

On successful WebRTC connection, this uses the RTCStats information to
determine if the connection is relayed via TURN. A followup CL will use
this to cap the bandwidth usage of relay connections.

Bug:  857287 
Change-Id: I30c39fd21d7a3cc82742a00d39fcf19f9fc9857c
Reviewed-on: https://chromium-review.googlesource.com/1117880
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574236}
[modify] https://crrev.com/32d3a2f9447417d82e5d03a27d345f74052e76c4/remoting/protocol/webrtc_transport.cc
[modify] https://crrev.com/32d3a2f9447417d82e5d03a27d345f74052e76c4/remoting/protocol/webrtc_transport.h

Project Member

Comment 2 by bugdroid1@chromium.org, 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

Status: Fixed (was: Started)
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