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.

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

feat: spawn webrtc connections on separate threads #6

Open
ThaUnknown opened this issue Aug 2, 2024 · 0 comments
Open

feat: spawn webrtc connections on separate threads #6

ThaUnknown opened this issue Aug 2, 2024 · 0 comments

Comments

@ThaUnknown
Copy link
Owner

have each webrtc connection on a separate thread, currently even across multiple connections this library will never exceed 1Gbit/s, if each connection was on a separate thread, this could easily exceed 5Gbit/s

many methods however are sync, so if this was spawned on node workers, sync-threads would need to be used to make said async calls sync, is this a bad idea perf wise?

next issue is data channels and callbacks, maybe use comlink?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant