A Compose for MySQL deployment allows for vertical scaling of both the database nodes and its TCP portals.
The vertical scaling option allows for memory and storage to be manually added to each database node. Vertical scaling is also the dimension that Compose Auto-scaling operates in.
In the Deployment Resources view for Compose for MySQL, the top panel shows the configured database nodes. Each row displays the node name, its location, and its IP address. In the top right, the memory and storage allocated to the nodes are displayed.
In the lower right of the panel are buttons to adjust the nodes. To add or reduce memory allocated to a Compose for MySQL deployment, click the Scale button. This takes you to the Scale Nodes view:
By adjusting the slider, you can raise or lower the memory allocated to the Redis nodes. The storage allocation is 10:1 with the selected memory allocation. When the slider is moved, the view updates with the new cost, per month, for the deployment.
Clicking Confirm triggers the rescaling of the deployment.
For Compose for MySQL there will be at least one TCP portal. Below is an example from the Scale TCP Portals view where the slider is set to scale it:
It is possible to add a TCP portal through the Security page, and if you have additional portals they will all be scaled to the new memory size.
If you find you do not need the resources currently provisioned to your deployment you can scale down the deployment. Compose auto-scaling will NOT automatically scale down or remove resources that you are not currently using.
Scaling down works similarly to scaling up. Moving the sliders to the left shows the difference in the cost, and the new monthly total.
Use the Security panel to remove any provisioned TCP/HAProxy portals from your deployment.
If this article didn't solve things, summon a human and get some help.
Updated about a year ago