Here you’ll find a complete list of all the database sizes available to you on PlanetScale.
If your needs exceed what is available here, we can easily spin up additional sizes for you. Just reach out and let us know. We also support sharding on Vitess clusters.
Network-attached storage databases come with autoscaling storage and have varying levels of compute power.
Processor
Memory
Transactions*
PS-10
1/8 vCPU
1 GB RAM
70
PS-20
1/4 vCPU
2 GB RAM
75
PS-40
1/2 vCPU
4 GB RAM
75
PS-80
1 vCPU
8 GB RAM
110
PS-160
2 vCPUs
16 GB RAM
158
PS-320
4 vCPUs
32 GB RAM
211
PS-400
8 vCPUs
32 GB RAM
211
PS-640
8 vCPUs
64 GB RAM
281
PS-700
16 vCPUs
32 GB RAM
211
PS-900
16 vCPUs
64 GB RAM
281
PS-1280
16 vCPUs
128 GB RAM
375
PS-1400
32 vCPUs
64 GB RAM
281
PS-1800
32 vCPUs
128 GB RAM
375
PS-2100
48 vCPUs
96 GB RAM
328
PS-2560
32 vCPUs
256 GB RAM
500
PS-2700
48 vCPUs
128 GB RAM
438
PS-2800
64 vCPUs
128 GB RAM
375
* Transactions refers to the number of simultaneous transactions your database can process, which is different than simultaneous connections.
This is also known as the transaction pool.
Metal databases are backed by locally-attached NVMe drives for storage, unlocking incredible performance and cost-efficiencies. Because the drives are locally-attached, you need to choose both your compute and storage resources when you create your database.
The storage options vary by cloud provided, so we break out the options into AWS and GCP sections.
Selecting the correct cluster size for your database can have a dramatic impact on how it performs and how much it costs.A good rule of thumb is when you notice CPU usage is consistently at or close to 100% for an extended period of time, you may benefit from upsizing your cluster. Conversely, if your CPU usage is consistently below 50%, you may be able to downsize. You can monitor your CPU usage by clicking on your database, clicking “Primary” in your architecture diagram, and referencing the chart under “Metrics and performance”.There are also special cases where you may want to temporarily upsize out of caution if you’re anticipating a large spike in traffic, such as during a launch or event. In these cases, you can easily upsize ahead of your event, and then downsize after. Changing cluster sizes is a seamless operation that requires no downtime.If you are migrating from an existing cloud provider with resource-based pricing, be sure to compare your currently selected instance with our available cluster sizes.Keep in mind, each database comes with a production branch with two replicas, as well as 1,440 hours worth of development branches (for Vitess databases). The development branches essentially equate to two extra “always on” databases. In many cases, you can deprecate your dev/staging databases that you pay extra for with other providers in favor of the development branches. In the end, this usually results in significant cost savings.Databases in PlanetScale also come with additional beneficial infrastructure that is not easily configured or available in other hosted database solutions. For more information on what is provisioned with each database, read our Vitess architecture and Postgres architecture docs.If you are unsure which plan or cluster size is right for your application, contact us to get further assistance.Our self-serve plans are flexible enough to handle the majority of customers. However, there are several use cases where you may need a more custom plan. This is where our Enterprise offerings shine.
As your application scales, upgrading or downgrading your cluster is a seamless operation that does not involve any downtime.To change cluster sizes, go to your PlanetScale dashboard, click on your database, click the gear icon that specifies your current cluster size, select the new cluster size, and click “Update”.The time it takes to change sizes depends on the size and region of your database. Larger databases may take 20 minutes to upsize/downsize. However, this is all done online, so you will not experience any downtime. Keep in mind, once you update your cluster size, you cannot change sizes again until the first size change completes.When you choose to change cluster size, we upgrade each of your replicas one by one: delete the tablet container, create a new tablet container of the new size, attach the persistent volume, start it up, and connect it to the primary. Once that’s complete, we fail the primary over to one of those new replicas, and do the same thing to the old primary.
