W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2019

Re: [webrtc-pc] (How) does SCTP handle CPU-bound congestion on JavaScript thread? (#2086)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Sat, 26 Jan 2019 11:45:41 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-457824741-1548503141-sysbot+gh@w3.org>
Whenever there are multiple streams of traffic on the "same wire" there will be competition, some packets will get dropped and some packets will arrive. @lgrahl Why do you think that if the buffer is shared one data channel would end up dominating it? (How does SCTP prioritize different channels?) Is your concern in general use cases, or is this only a concern in edge cases such as if one data channel is sending messages the size of the entire buffer, leaving no room for other messages, and SCTP prioritizing the same channel every time? (Follow-up question: If there is a legitimate concern, is there no good way for the application to get around it?)

The fix I'm proposing does not change how SCTP work but it does provide a feedback mechanism between the JS thread and the network thread. JS will still have "onmessage" fire in accordance to SCTP receiving messages, it will however ensure that the buffer does not get emptied faster than it is processed by the application.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2086#issuecomment-457824741 using your GitHub account
Received on Saturday, 26 January 2019 11:45:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 15:15:01 UTC