-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
Use uWebSocket.js encrease I/O productivity few times #310
Comments
Will be good 👍 |
It's good to have it back, didn't know it was already publicly released with binaries, had checked 2 weeks back. Will implemented in uwt soon. Or if @feross agrees, just merge all back into this module using uWebSockets |
Great! @DiegoRBaquero please keep in mind HTTPS support. Using Nginx as HTTPS proxy in front of the tracker may dramatically decrease I/O productivity. |
We decided to create our own open source high-performance implementation of WebTorrent tracker using uWebSockets.js: https://github.com/Novage/wt-tracker It can handle 100k peers (no SSL) using 1.2Gb of memory and 50% of a single CPU core. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
Is this relevant? If so, can implement this enhancement? I'm not sure if uWebSockets.js has compatibility with all systems. Should we implement this as an additional option for ws or a replacement? |
P2P technologies should be scalable and efficient when it goes to high loads.
The goal is to rewrite the code to be able to use uWebSockets.js HTTP/HTTPS/WebSocket server as an option for HTTP I/O. At least to refactor the code to use the maximum of the logic from this project in a new tracker project that will be based on uWebSockets.js I/O.
This article and this one describe how uWebSockets.js is a few times more efficient in I/O than any other Node.js solutions and even C/C++/Golang solutions. Also, it will lead to the use of the built-in uWebSockets.js HTTPS support and remove the need for Nginx in front of the tracker.
The benefit is that public and private trackers will be able to serve a few times more peers.
It will help to solve #308, #299, #269 (uWebTorrent tracker is written using
uws
and uWebSockets.js is the successor of it written by the same author) and other related issues.The text was updated successfully, but these errors were encountered: