Temporary Usage Spikes: When's the threshold for scaling up the droplet?
Contemplating a strategy for dealing painlessly (ie. automatically) with temporary traffic spikes on a droplet running a LAMP stack. (On a basic droplet, and prefer to keep the size until ongoing loads increase.) I realize you could replicate the droplet and load-balance horizontally, however that may be a bit more than I care to deal with at the moment.
I notice the API allows calls for resizing the droplet – and that there’s a reversible mode of resizing (that only adds CPU & RAM). I’m thinking about setting up a system to monitor the server load that issues a resize request when a certain threshold is crossed, and then revert when the load returns to normal. Does that seem like a sensible approach? And would it be considered good practice by DigitalOcean’s side If I were to resize frequently?
While we’re on the topic, I’d love to hear more thoughts on what you consider a threshold high enough to merit resizing (level/duration). I’m thinking of probing both the overall CPU/RAM load and getting specific performance data from Apache/MySQL for threshold factors. Please share any experiences or pointers for further digging. Thanks!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.