WebRTC streaming performance
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 546
- Avg merge
- 8h 18m
- Merged PRs (30d)
- 16
Description
The performance dashboard shows that the median streaming performance of WebRTC in Node.js is an order of magnitude slower than TCP.
We should look into why this is.
Support for WebRTC is provided by node-datachannel (we are using a temporary fork at https://github.com/ipshipyard/js-node-datachannel until https://github.com/murat-dogan/node-datachannel/pull/256 is merged).
node-datachannel uses libdatachannel which then uses libjuice so the bottleneck is in there somewhere.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked performance dashboard and compare the WebRTC and TCP streaming results in Node.js. Trace the path through the temporary node-datachannel fork, libdatachannel, and libjuice; done means identifying where the performance gap occurs and documenting the evidence or next action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- networking, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100