Database Scaling

Databases can be resized using the aptible db:restart command, or via the Dashboard.

Database scaling is performed with minimal downtime (usually less than 1 minute).

RAM Scaling

Database Containers can be resized at any time. Supported container sizes, in MB, are 512, 1024, 2048, 4096, 7168, 15360, 30720, 61440, 153600, and 245760.



When you resize up, scaling may take a while to complete if Aptible needs to provision additional capacity (i.e. additional EC2 instances). Overall, the process can take up to an hour.

However, Database downtime will always be minimized: Aptible waits until new capacity is available before shutting down your database, so downtime will remain on the order of 1 minute, regardless of how long it takes to provision new capacity.

Disk Scaling

Database Disks can be scaled up to 16384GB. Database Disks can be resized at most once a day, and can only be resized up (i.e. you cannot shrink your Database Disk).

If you do need to scale Database Disk down, you can either dump and restore to a smaller Database or create a replica and failover. Refer to our Supported Databases documentation to see if replication and failover is supported for your Database type.

I/O Performance

As of February 12, 2021, Aptible uses AWS gp3 volumes, which provide a minimum baseline IOPS performance of 3,000 IOPS no matter how small your volume is.

If you want to increase the IOPS for your GP3 volume, you may do so live with no impact to the availability of your Database, by using the aptible db:modify command. The maximum IOPS is 16,000, but you must meet a minimum ratio of 1 GB disk size per 500 IOPS. For example, to reach 16,000 IOPS, you must have at least a 32 GB or larger disk.

Databases created before February 12, 2021 are using gp2 volumes, which provide a baseline IOPS performance of 3 IOPS / GB of disk, with a minimum allocation of 100 IOPS. In addition to the baseline performance, gp2 volumes also offer burst IOPS capacity up to 3,000 IOPS, which lets you exceed the baseline performance for a period of time.

For production databases, we strongly recommend that you verify that your Database's I/O activity (see Metrics) remains below the volume's baseline IOPS performance.



If using gp2 volumes, you should not rely on the volume's burst capacity during normal activity. Doing so is likely to cause your performance to drop once you exhaust the volume's burst capacity, which is likely to cause your app to go down as a result. gp3 volumes do not offer burst capacity.

Throughput performance

GP3 volumes have a default throughput performance of 125MiB/s, and can be scaled up to 1,000MiB/s by contacting Aptible Support.

GP2 volumes have a maximum throughput performance of between 128MiB/s and 250MiB/s, depending on volume size. Volumes smaller or equal to 170gb in size are allocated 128MiB/s of throughput. The throughput scales up until you reach a volume size of 334gb. At 334gb in size, or larger, you have the full 250MiB/s performance possible with a GP2 volume. If you need more throughput, you may upgrade to a GP3 volume at any time by using the aptible db:modify command.