undefined | Better HN

0 pointsdetaro9y ago0 comments

> A: Peer5 works with whatever bandwidth is free for upstream use and will not impact other applications that require uploads at the same time as Peer5.

That would also require WebRTC traffic to be properly tagged as low-priority and general consumer gear being any good at QoS, neither of which is the case. Of course parallel uploads can and will have a negative effect.

0 comments

1 comments · 1 top-level

shacharz9y ago

Part of WebRTC's requirements [1] is to be fair on competing TCP connections. This is a very good point, because I agree with you that in general parallel connections cause each connection to have less throughput, but if those connections have a mutual goal to download the same content it can actually increase the overall throughput than downloading that content via a single TCP connection. That's especially true when those connections are to different sources which can workaround specific network issues you might have in a single connection.

Actually the value proposition for our customers is to improve the QoS. And we've shown that's the case in customer case studies.

[1] https://wiki.tools.ietf.org/html/draft-ietf-rtcweb-data-chan...

j / k navigate · click thread line to collapse