PostgreSQL Resources and Scaling
PostgreSQL resource scaling
A PostgreSQL deployment allows for vertical scaling:
The vertical scaling option allows for memory and storage to be manually added to each database node. VVertical scaling is also the dimension that Compose Auto-scaling operates in.
Adding memory and storage to PostgreSQL nodes
In the Deployment Resources view for PostgreSQL, the top panel shows the database nodes configured. Each row displays the node name, location, and 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 PostgreSQL deployment, click the Scale button. This takes you to the Scale Nodes view:
By adjusting the slider, you can raise or lower the storage allocated to the PostgreSQL nodes. The memory 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 will trigger the rescaling of the deployment.
Adding memory to portals
For PostgreSQL, there will be at least one TCP portal. Below is an example from the Deployment Resources view where one TCP portal is configured:
Clicking Scale takes you to a slider where you can increase or decrease the memory allocated to the mongos routers and see the projected monthly cost of those changes. Clicking Confirm puts those changes in place.
Adding Additional HAProxy Portals
The Security panel includes a list of the currently configured HAProxy portals.
Clicking on Add TCP portal will bring up a dialog asking you to confirm the additional portal including it's billing rate of $4.50/mo. Clicking Create will start the provisioning process. Once the process is complete, the portal's connection string will appear on the deployment's Overview.
Manually Scaling Down
Memory and Storage
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.
Still Need Help?
If this article didn't solve things, summon a human and get some help
Updated over 3 years ago