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

Please help - 1000 ppl crash (how to scale) #22

Open
breebee opened this issue Oct 14, 2019 · 1 comment
Open

Please help - 1000 ppl crash (how to scale) #22

breebee opened this issue Oct 14, 2019 · 1 comment

Comments

@breebee
Copy link

breebee commented Oct 14, 2019

This project is amazing, I have tested various times with success. Today however we tried to launch a broadcast which unexpectedly hit almost 1000 users. Everything crashed, and would not pick itself back up.. Please let me hire you to help me scale this properly. I have the following ideas on how to optimize/scale

  1. break down 7 manifest items into 2/3 so that theres less files to propogate and re-seed in p2p
  2. find a way that I can actually scale the live torrent system. For example folder sync accross multiple servers as root seeds. Please help as soon as possible I can hire via upwork or paypal services. You can contact me directly at [email protected]
@pldubouilh
Copy link
Owner

hello - I think the main issue scaling wise would be scaling the websocket "trackers". it's currently only relying on 1 tracker and I think the usage could get fairly high fairly quick.

Ideally you'd make the peers talk to each other (peer exchange in bittorrent), or even pre-send chunks of the stream, but that's outside of the scope of bittorrent (and I think webtorrent doesn't keep data-channels connections open nor available to be used at a higher level). That's not implemented though, and I'm not available for hiring

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

2 participants