A RethinkDB deployment allows for vertical scaling of database nodes, Rethink Proxies, and SSH portals.
The vertical scaling option allows for memory and storage to be added to each database node. Vertical scaling is the dimension that Compose Auto-scaling operates in.
In the Deployment Resources view for RethinkDB, 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 is displayed.
List of resources for a RethinkDB deployment.
In the lower right of the panel are buttons to adjust the nodes. To add (or reduce) memory allocated to a RethinkDB deployment, click the Scale button. This will take you to the Scale Nodes view:
The Scale Nodes view.
By adjusting the slider, you can raise or lower the storage allocated to the RethinkDB nodes. The memory allocation is 10:1 with the selected memory allocation. When the slider is moved, the view will update with the new cost, per month, for the deployment.
Scaling nodes with more resources.
Clicking Confirm will trigger the rescaling of the deployment.
For RethinkDB there will be one Rethink Proxy and zero or more SSH portals. Below is an example from the Scale Rethink Proxies view with the slider set to scale it:
Scaling up a portal.
The Scale SSH Portal view is similar, and if there is more than one SSH portal configured for the deployment, both with be scaled to the new memory size.
If this article didn't solve things, summon a human and get some help!