-
Notifications
You must be signed in to change notification settings - Fork 49
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
Scalability with limited amount of UDP port for kraken #23
Comments
hey bro can u help me install kraken on vps nginx |
Yes, we use many instances to balance the traffic. That we have a monitor API to monitor all the kraken instances server load, and direct participants in the same room to the same instance. |
@cedricfung Thanks for the quick reply, is there any guide in using the monitor feature of kraken? |
The monitor is another piece of code, that monitors the instance resource usage using Google Compute Engine API. We didn't open source those code yet, because they are coupled with our main repo. And we have the plan to make the monitor open source, but busy at other stuffs. |
@sooxt98 Why do I not see anyone? I checked in twice to make sure, but there is something wrong |
I saw your blog post, it stated each participants will consume 1 udp port on kraken, which means i could only have maximum of 48127 participants online simultaneously (common available udp port range 1024 to 49151), How to scale it up to allow more than that amount of users?
Here's the idea i got, make a daemon that actively monitor the usage of the kraken UDP port availability, and magically use a Load Balancing to distribute the traffic to others instance
The text was updated successfully, but these errors were encountered: