NoteFor PlanetScale for Postgres clusters launched on PlanetScale Metal instances, storage is scaled by directly scaling the cluster instance size. Storage autoscaling is not available for Metal clusters. To learn more see the documentation for PlanetScale Metal
Configuring storage settings
You must be a database or organization administrator to modify these settings. Adjusting these settings may incur additional charges. To learn more about pricing for storage, see pricing.1
From the PlanetScale organization dashboard, select the desired database
2
Navigate to the Cluster configuration page from the menu on the left
3
Choose the branch whose storage settings you’d like to configure in the “Branch” dropdown
4
Select the Storage tab
5
Configure your disk size and autoscaling settings
6
Set your storage limit as needed
7
Click “Queue storage changes”
8
Once you’re ready to apply the changes, click “Apply changes”
Disk configuration
Disk size
Configure the minimum disk size for your database cluster. This setting determines the initial storage capacity allocated to your database. The disk size is specified in GB and serves as the baseline storage allocation for your cluster.NoteThe maximum disk size for network-attached storage is 16384 GB (16 TiB).
Enable autoscaling
NotePlanetScale storage autoscaling is only for network-attached storage database clusters. For [PlanetScale Metal
Autoscaling thresholds and behaviors
Disk size utilization thresholdsVolume size | % used |
---|---|
< 4 TiB | 70% |
> 4 TiB | 90% |
- Cluster storage can only scale once in a 6 hour period
- Cluster storage scales proportionally based on current size
- Smaller disks receive larger percentage increases, while larger disks receive smaller percentage increases
- All disks grow by a minimum of 50% when autoscaling occurs
- If you need to scale cluster storage by more than 200% within 24 hours, manually scale disk size ahead of time
- Autoscaling will not scale past your configured [Storage limit
Storage limit
The storage limit sets the maximum amount of storage that can be allocated to your database cluster through autoscaling. This acts as a ceiling to prevent unlimited storage growth and helps control costs. When autoscaling is enabled, your storage can grow from the minimum disk size up to the storage limit you specify. The storage limit should be set higher than your initial disk size to allow for growth while providing a reasonable upper bound for your storage costs.NoteThe maximum disk size for network-attached storage is 16384 GB (16 TiB).
IOPS
Configure the maximum input/output operations per second for your database. This will be limited by your database cluster size and disk size.Storage volume type and IOPS
Storage type | Default IOPS | Maximum IOPS |
---|---|---|
AWS gp3 | 3000 | 16,000 (at 32GB or larger disk size) |
Bandwidth
The maximum amount of data that can be read or written to your database in a single second. This will be limited by your database cluster size and configured IOPS.Storage volume type and bandwidth
Storage type | Default bandwidth | Maximum bandwidth |
---|---|---|
AWS gp3 | 125 MiB/s | 1,000 MiB/s (at 4,000 IOPS or higher) |
Storage throughput limits
For databases created on AWS-based clusters the maximum configurable throughput your cluster can support is based on CPU architecture and cluster size.CPU Architecture | Cluster Size | Maximum Throughput (in MiB/s) |
---|---|---|
AWS x86-64 | PS-DEV, PS-10, PS-20, PS-40, PS-80, PS-160, PS-320, PS-640, PS-1280, PS-2560 | 1000 |
AWS aarch64/ARM64 | PS-DEV, PS-10, PS-20, PS-40, PS-80, PS-160, PS-320, PS-640, PS-1280 | 593 |
AWS aarch64/ARM64 | PS-2560 | 1000 |