Open Bug 1873395 Opened 2 years ago Updated 2 years ago

Data channel multiplex performance

Categories

(Core :: WebRTC: Networking, enhancement)

Firefox 121
Desktop
Windows 11
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: xenovationdirector, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Steps to reproduce:

  1. Setup peer connection (I did not test locally)
  2. Limit upload speed of peer A/download speed of peer B to 30 kBps
  3. Create two data channel with config {ordered: false}
  4. Continuously Fill the buffer to decent amount by calling .send with tight SetInterval timing on the first data channel on peer A
  5. Send any message on the second data channel on peer A

Actual results:

When the network is congested (< 30 kBps), on step 5, firefox initiate the process of sending that packet way too slow causing a lot of delay for messages sent on different data channels.

With 30 kBps speed cap, it took around 3.5 seconds before firefox initiate the packet sending process but chromium and IOS safari browser took less than <100ms.

The speed of initiating sending packet on different data channels go faster as I increase the bandwidth cap, when I uncap the bandwidth, the speed is decent but still slower than chromium and safari browser.

Expected results:

The multiplex performance should be improved.

Component: WebRTC → WebRTC: Networking
OS: Unspecified → Windows 11
Hardware: Unspecified → Desktop
You need to log in before you can comment on or make changes to this bug.