Scaling Disk, RAM, and CPU

Resource Breakdown

Databases for MySQL deployments have three data members in a cluster, and resources are allocated to members equally. For example, the minimum storage of a MySQL deployment is 20,480 MB, which equates to an initial size of 6,826 MB per member. The minimum RAM for a MySQL deployment is 3072 MB, which equates to an initial allocation of 1024 MB per member.

Billing is based on the total amount of resources that are allocated to the service.

Scaling Considerations

• Scaling your deployment up might cause your databases to restart. If you scale RAM or CPU and your deployment needs to be moved to a host with more capacity, then the databases are restarted as part of the move.

• Scaling down RAM or CPU does not trigger database restarts.

• Disk cannot be scaled down.

• A few scaling operations can be more long running than others. Enabling dedicated cores moves your deployment to its own host and can take longer than just adding more cores. Similarly, drastically increasing CPU, RAM, or Disk can take longer than smaller increases to account for provisioning more underlying hardware resources.

• Scaling operations are logged in IBM Cloud® Activity Tracker.

• If you find consistent trends in resource usage or would like to set up scaling when certain resource thresholds are reached, check out enabling autoscaling on your deployment.

Scaling in the UI

A visual representation of your data members and their resource allocation is available on the Resources tab of your deployment's Manage page.

Adjust the slider to increase or decrease the resources that are allocated to your service. The slider controls how much memory or disk is allocated per member. The UI shows the total allocated memory or disk for the position of the slider. Click Scale to trigger the scaling operations and return to the dashboard overview.

The UI currently uses a coarser-grained resolution for scaling than the CLI or API commands. Use the API or CLI to scale if the stops on the slider do not meet your size requirements.

Scaling in the CLI

The Cloud Databases CLI plug-in supports viewing and scaling the resources on your deployment. To scale any of the available resource groups, use cdb deployment-groups-set command.

For example, the command to view the resource groups for a deployment named "example-deployment" is,

ibmcloud cdb deployment-groups example-deployment

and produces the following output:

Group   member
Count   3
|
+   Memory
|   Allocation              3072mb
|   Allocation per member   1024mb
|   Minimum                 1024mb
|   Step Size               256mb
|   Adjustable              true
|
+   CPU
|   Allocation              6
|   Allocation per member   3
|   Minimum                 6
|   Step Size               2
|   Adjustable              true
|
+   Disk
|   Allocation              15360mb
|   Allocation per member   5120mb
|   Minimum                 15360mb
|   Step Size               15360mb
|   Adjustable              true

The deployment has three members, with 3072 MB of RAM and 15360 MB of disk allocated in total. The "per member" allocation is 1024 MB of RAM and 5120 MB of disk. The minimum value is the lowest the total allocation can be set. The step size is the smallest amount by which the total allocation can be adjusted.

The cdb deployment-groups-set command allows either the total RAM or total disk allocation to be set, in MB. For example, to scale the memory of the "example-deployment" to 2048 MB of RAM for each memory member (for a total memory of 4096 MB), you use the command

ibmcloud cdb deployment-groups-set example-deployment member --memory 4096

Scaling in the API

The Foundation Endpoint shown on the Overview panel Deployment details of your service provides the base URL to access this deployment through the API. Use it with the /groups endpoint if you need to manage or automate scaling programmatically.

To view the current and scalable resources on a deployment, use

curl -X GET -H "Authorization: Bearer $APIKEY" 'https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/groups'

To scale the memory of a deployment to 2048 MB of RAM for each memory member (for a total memory of 4096 MB).

curl -X PATCH 'https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/groups/member' \
-H "Authorization: Bearer $APIKEY" \
-H "Content-Type: application/json" \
-d '{"memory": {
        "allocation_mb": 4096
      }
    }'

More information is in the API Reference.