Open pluto00987 opened 10 months ago
@PJNorrisS1 @PunitTailor55 @garanews Any suggestions for @pluto00987
That's a lot of players! DB for sure separate and don't consider using sqlite for that many players. Also we find the scoreboard websocket intensive so we now only enable the scoreboard for Admins only, which dramatically will reduce the load on the box.
We still keep it in a docker container. We run between 20-40 players, but the key difference here is that we may have 10 games or so running globally at the same time - so we beefed up our resources. They are all separate RTB docker containers on the same box with some internal coded platform we manage everything from.
I'm looking for some general guidance and/or recommendations on how to scale a RtB server. Or, how well it scales in general with larger hardware. I have seen Issue #177 from and realize I'm kind of asking the same loaded question, but any updated or more specific suggestions beyond that are appreciated. That answer is ~5 years old :)
For context, we've been using the provided docker setup to run some smaller events (around 15 people) and it has worked great so far on 2 vCPU and 2GiB RAM. We're currently discussing the possibility of running an event at a conference where there would be around 300-400 participants and want to ensure we build a server that can handle that.
So far I've assumed or seen suggestions to:
I would appreciate any comments on how beneficial any of the above would or wouldn't be, either separate or together. I'd also love to hear from anyone who has tried any of those and their experience or thoughts on the matter. Or anyone that's run some larger events and their experience there.
Thanks much!