mirror of
https://github.com/asapach/peerflix-server.git
synced 2026-04-25 14:45:50 +03:00
[GH-ISSUE #115] [Question] How many users can peerflix-server handle? #312
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AurumProject on GitHub (May 12, 2017).
Original GitHub issue: https://github.com/asapach/peerflix-server/issues/115
Hi all, first sorry for my english, maybe it's a noob question but i would like to know if anyone had how many users peerflix can handle withouth crashing? Streaming the same torrent? etc..
The point is to know what are the best / recommended server requirements to handle 10,000 request from the same stream, at the same time. And your experience running a public peerflix-server.
Thank you all,
@asapach commented on GitHub (May 12, 2017):
It's definitely not designed for scale. I don't think you can get more than 10 users to stream comfortably.
@AurumProject commented on GitHub (May 13, 2017):
What is the first problem that comes to your mind when serving more than 10 users? The only limitations that i see is Ram, HDD, Bandwith..
Can you explain more?
Thanks for your quickly answer @asapach .
@asapach commented on GitHub (May 13, 2017):
Actually the first limit you will run into is CPU, because it's single-threaded. Every peer and client require a certain amount of CPU resources to keep them happy, and once it's exhausted everything becomes sluggish. It's less of a problem when the torrent is fully downloaded, because the most expensive part is over.
Slow HDD can be a bottleneck, as well as limited IOPS on a virtual server.
You can run into the default V8 limit of ~1.6GB RAM that Node has if CPU or HDD don't keep up.
Bandwidth is a constant issue, regardless of how many users you have.