Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WebRTC streaming performance #3033

Open
achingbrain opened this issue Mar 5, 2025 · 1 comment
Open

WebRTC streaming performance #3033

achingbrain opened this issue Mar 5, 2025 · 1 comment
Labels
good first issue Good issue for new contributors help wanted Seeking public contribution on this issue

Comments

@achingbrain
Copy link
Member

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 murat-dogan/node-datachannel#256 is merged).

node-datachannel uses libdatachannel which then uses libjuice so the bottleneck is in there somewhere.
@achingbrain achingbrain added need/triage Needs initial labeling and prioritization help wanted Seeking public contribution on this issue good first issue Good issue for new contributors and removed need/triage Needs initial labeling and prioritization labels Mar 5, 2025
@07Vaishnavi-Singh
Copy link

Hey @achingbrain I am new to libp2p but want to learn and contribute to this issue can you please assign me this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good issue for new contributors help wanted Seeking public contribution on this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@achingbrain @07Vaishnavi-Singh