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

Load balancing for bittorrent-tracker? #299

Closed
brooklyn097 opened this issue Oct 27, 2018 · 9 comments
Closed

Load balancing for bittorrent-tracker? #299

brooklyn097 opened this issue Oct 27, 2018 · 9 comments
Labels

Comments

@brooklyn097
Copy link

Hi, this could be a dumb question but is there a way to do balancing for the tracker?

Thanks for reading!

@DiegoRBaquero
Copy link
Member

DiegoRBaquero commented Oct 27, 2018 via email

@brooklyn097
Copy link
Author

@DiegoRBaquero Thanks for your answer. Btw, is it possible to use 0.0.0.0 address for server listening? I've tried and saw this message on error event when start the application:

bind EINVAL 0.0.0.0:

But I still accessible to /stats page so i don't know whether there is any error cause by this.

@DiegoRBaquero
Copy link
Member

Mmmm, it should work, i don't see why not, unless you don't have permission to bind to it.

@brooklyn097
Copy link
Author

Yes you’re right! It shown an error but it actually work fine.

@mullerivan
Copy link

mullerivan commented Feb 12, 2019

@brooklyn097 I have a tracker that scale and balance the load on several servers
hit me an email [email protected]

@mrlika
Copy link

mrlika commented Feb 27, 2019

We decided to create our own open source high-performance implementation of WebTorrent tracker: https://github.com/Novage/wt-tracker

Our tests show that to handle 100k peers (no SSL) it requires 1.2Gb of memory and 50% of a single CPU core.

It is written using uWebSockets.js that allows efficiently process WebSockets connections and optimized algorithms that use less CPU than other similar trackers.

Waiting for your feedback.

@brooklyn097
Copy link
Author

We decided to create our own open source high-performance implementation of WebTorrent tracker: https://github.com/Novage/wt-tracker

Our tests show that to handle 100k peers (no SSL) it requires 1.2Gb of memory and 50% of a single CPU core.

It is written using uWebSockets.js that allows efficiently process WebSockets connections and optimized algorithms that use less CPU than other similar trackers.

Waiting for your feedback.

Cool, let's test!!!

@github-actions
Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@github-actions github-actions bot added the stale label Jul 22, 2021
@alxhotel
Copy link
Member

Closing in favor of #354

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

No branches or pull requests

5 participants