search

webtorrent / bittorrent-tracker

🌊 Simple, robust, BitTorrent tracker (client & server) implementation
https://webtorrent.io
MIT License
1.78k stars 319 forks source link

Load balancing for bittorrent-tracker? #299

Closed brooklyn097 closed 3 years ago

brooklyn097 commented 6 years ago

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

Thanks for reading!

DiegoRBaquero commented 6 years ago

Not at the moment as the peers are tracked in memory. Something like redis would need to be the store first

On Oct 27, 2018, at 12:41 PM, brooklyn097 notifications@github.com wrote:

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

Thanks for reading!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

brooklyn097 commented 6 years ago

@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 commented 5 years ago

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

brooklyn097 commented 5 years ago

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

mullerivan commented 5 years ago

@brooklyn097 I have a tracker that scale and balance the load on several servers hit me an email mullerivan@gmail.com

mrlika commented 5 years ago

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 commented 5 years ago

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[bot] commented 3 years ago

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

alxhotel commented 3 years ago

Closing in favor of #354