![]() Your users in the rooms will have a brief freeze/voice drop while the users roll to the new servers. If you notice performance issues, you can ad hoc update the stack up more from a c4.large to c5.2xlarge (?). For example 1 hour before your event, update the stack from a t3.medium to c4.large (?). If your instance is in Offline mode, manually update the stack to Online and wait 10 minutes.Īfter, at least 1 hour before event, manually update the stack to scale up your AWS Server Type. Then switch back to Online when beginning development again. When not in use, set your instance to Offline mode. Before your event: Developmentįor development with only a few users connecting + setting rooms + scenes, we recommend at least a t3.medium instance (?). Also use a Cloudflare worker as your content CDN. When no one is using your hub, turn your hub to Offline mode or a small instance type like t3.medium. Our recommendation to minimize costs for automatic settings is to turn database pausing on by default. To more accurately predict future costs use AWS Cost Explorer for your instance. To roughly estimate your costs, check out our Estimated Cost Charts (alpha). If you'd like to maximize your cost savings, you can perform a stack update to switch the stack into "Offline" mode when you are not using it, though this likely unnecessary except for cases where you are running at a higher capacity settings than the defaults. In your hub's admin console, go to the "Data Transfer" page to see how. Note that you can significantly save data transfer charges by switching your CDN to Cloudflare.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |