Workspace Scaling
On this page
Overview
When deploying databases in the cloud, users expect to be able to scale resources up or down depending on their workload.
SingleStoreDB Cloud has a unique architecture which offers the flexibility to scale resources dynamically, for both read and write workloads.
Compute workspaces can be scaled up or down to accommodate changing workloads.
SingleStoreDB is a distributed SQL database, so scaling operations can be performed online by adding or removing resources without impacting the overall deployment.

How Scaling Works
A SingleStoreDBcompute “workspace” is made up of individual nodes, which allow an even distribution of jobs across the underlying cloud resources.
When a user triggers a scale up or scale down operation SingleStoreDB automatically determines the number of compute resources required and adjusts the size of the workspace on the fly.
When scaling up, SingleStoreDB adds compute resources to the existing workspace, increasing the performance and capacity of the compute deployment.
When scaling down, SingleStoreDB removes a portion of the resources available for the workspace, without impacting the availability of the workspace itself.
Some databases allow online scaling within a single machine type, but workloads are limited by the maximum size of a host.
Scaling - Cloud Portal UI
Scaling up or down can be triggered through the UI or Management API.
This will open a menu where the user can choose a target workspace size.
Scaling - Management API
Scaling up or down through the management API can be done by using WorkspaceUpdate size
.
High Availability
Critical workloads need to stay online, even when scaling the underlying resources.
Scaling Impact on Performance
Scaling operations trigger the online addition or removal of compute resources, as well as a redistribution of data to ensure even performance across the compute workspace.
For large deployments with heavy active workloads the time required to complete the scaling operation may increase as a larger volume of active data needs to be redistributed within the workspace.
Progressive Scaling
A further enhancement to the way SingleStoreDB scales workloads is progressive scaling.
The net effect is faster scaling of resources, and a smaller impact to workloads when scaling up read and write capacity.
Billing
Workspaces consume compute credits while they are running.
Workspace scaling does not affect the storage costs, as storage is charged based on the average number of monthly GB stored, which does not change when workspaces are scaled up or down.
Last modified: August 8, 2023