Compose Database-as-a-Service Help and Documentation

Everything you need to know about Compose, Hosted or Enterprise, is here in our help system. Whether you run one database for your businesses' sole application or six different databases to support an entire corporation, we've got the information you need.

Scylla Resources and Scaling

A Scylla deployment features vertical scaling of database nodes and TCP portals, and horizonal scaling, which allows you to add portals.

ScyllaDB Resource Scaling

Vertical Scaling

The vertical scaling option allows for memory and storage to be manually added to each database node. Vertical scaling is the dimension that Compose Auto-scaling operates in.

Portals

All Scylla deployments support adding TCP portals, as well as adding memory resources to those portals.

Adding Memory and Storage to Scylla Nodes

In the Deployment Resources view for Scylla, the Nodes 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.

The _Deployment Resources_ page.

The Deployment Resources page.

In the lower right of the panel are buttons to adjust the nodes. To add or reduce memory allocated to a Scylla deployment, click Scale. This takes you to the Scale Nodes view:

The _Scale Nodes_ view.

The Scale Nodes view.

By adjusting the slider, you can raise or lower the storage allocated to the Scylla 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.

Scaling a node dialogue.

Scaling a node dialogue.

Clicking Confirm triggers the rescaling of the deployment.

Adding Memory to Portals

For Scylla there will be at least three TCP portals. Below is an example from the Scale TCP Portals view where the slider is set to scale the portals:

Scaling a TCP Portal dialogue.

Scaling a TCP Portal dialogue.

You can add more TCP portals to your deployment from the Settings view. All the portals will be scaled to the new memory size.

Manually Scaling Down

If you find you do not need the resources currently provisioned to your deployment you can manually 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, as in the example from scaling down the TCP portal below:

Scaling a TCP Portal down.

Scaling a TCP Portal down.

The sliders for the nodes work the same way.

Removing a Node

If you need to remove a node entirely, please contact support.


Still Need Help?

If this article didn't solve things, summon a human and get some help.