What is the best server size for Personal with 50 CCU to 150 CCU attending my event? #3105
-
we are planning on creating an event using hubs cloud running on aws, and we're having some difficulties to decide on what will be the best server option - based on the https://hubs.mozilla.com/docs/hubs-cloud-aws-estimated-cost-charts.html and https://hubs.mozilla.com/docs/hubs-cloud-aws-estimated-ccu-limits.html since we are not able to consider the estimate cost, we created 2 possibles scenarios, and we like to know which serverr type would be appropriate for each 1 - 2 equal rooms with maximum of 25 active users each (50 CCU) 2 - 6 equal rooms with maximum of 25 active users each (150 CCU) our event will happen during a month, with only 1 scene (the same scene in multiple rooms), with some specifics events during this. It has to be online for 30 days, but in some dates we will have specific actions, like a presentation, that we expect a bigger flow of users. you guys wrote that the recommended for an event is the c4.large, but on the CCU table, it seems to be very similar to the t3.medium, which is much cheaper - we are very confused with this docs and the numbers in that our budget only allow to use the Hubs Personal, is it ok for an event like we described? thank you very much, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Brilliant deduction. I'd suggest reading this part of the Minimizing Cost Documentation to understand the tools you have updating the stack in an event context: Hubs Docs: Minimizing Costs an Event User Story |
Beta Was this translation helpful? Give feedback.
Brilliant deduction.
IMO a Personal instance will work fine for your use case. A t3.medium sounds great for the off time, though during an event/presentation, I'd "update the stack" to a c4.large to ensure consistent performance.- Read correction belowI'd suggest reading this part of the Minimizing Cost Documentation to understand the tools you have updating the stack in an event context: Hubs Docs: Minimizing Costs an Event User Story