From 6aa7c370e6621582440bf8abea61babc30e7261c Mon Sep 17 00:00:00 2001
From: PlanetScale Actions Bot <operations+build@planetscale.com>
Date: Fri, 12 Jul 2024 21:43:07 +0000
Subject: [PATCH] docs: upstream
https://github.com/planetscale/www/commit/1287a291421e04c7ccd4f573ff460a7408d70c2e
---
docs/concepts/planetscale-plans.md | 43 +++++++++++----------
docs/reference/planetscale-system-limits.md | 20 +++++++++-
2 files changed, 42 insertions(+), 21 deletions(-)
diff --git a/docs/concepts/planetscale-plans.md b/docs/concepts/planetscale-plans.md
index f4a2b387..4a87f75c 100644
--- a/docs/concepts/planetscale-plans.md
+++ b/docs/concepts/planetscale-plans.md
@@ -1,7 +1,7 @@
---
title: 'PlanetScale plans'
subtitle: 'Learn about the different products and plans we offer: Scaler Pro and Enterprise'
-date: '2024-05-03'
+date: '2024-07-12'
---
## Overview
@@ -14,25 +14,28 @@ Our plans are split into two general offerings: [Scaler Pro (self-serve)](#scale
The **Scaler Pro** plan is broken down by cluster size, which have varying levels of compute power.
-| | **Processor** | **Memory** |
-| ----------- | ------------- | ---------- |
-| **PS-10** | 1/8 vCPU | 1 GB RAM |
-| **PS-20** | 1/4 vCPU | 2 GB RAM |
-| **PS-40** | 1/2 vCPU | 4 GB RAM |
-| **PS-80** | 1 vCPU | 8 GB RAM |
-| **PS-160** | 2 vCPU | 16 GB RAM |
-| **PS-320** | 4 vCPU | 32 GB RAM |
-| **PS-400** | 8 vCPU | 32 GB RAM |
-| **PS-640** | 8 vCPU | 64 GB RAM |
-| **PS-700** | 16 vCPU | 32 GB RAM |
-| **PS-900** | 16 vCPU | 64 GB RAM |
-| **PS-1280** | 16 vCPU | 128 GB RAM |
-| **PS-1400** | 32 vCPU | 64 GB RAM |
-| **PS-1800** | 32 vCPU | 128 GB RAM |
-| **PS-2100** | 48 vCPU | 96 GB RAM |
-| **PS-2560** | 32 vCPU | 256 GB RAM |
-| **PS-2700** | 48 vCPU | 128 GB RAM |
-| **PS-2800** | 64 vCPU | 128 GB RAM |
+| | **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 vCPU | 16 GB RAM | 158 |
+| **PS-320** | 4 vCPU | 32 GB RAM | 211 |
+| **PS-400** | 8 vCPU | 32 GB RAM | 211 |
+| **PS-640** | 8 vCPU | 64 GB RAM | 281 |
+| **PS-700** | 16 vCPU | 32 GB RAM | 211 |
+| **PS-900** | 16 vCPU | 64 GB RAM | 281 |
+| **PS-1280** | 16 vCPU | 128 GB RAM | 375 |
+| **PS-1400** | 32 vCPU | 64 GB RAM | 281 |
+| **PS-1800** | 32 vCPU | 128 GB RAM | 375 |
+| **PS-2100** | 48 vCPU | 96 GB RAM | 328 |
+| **PS-2560** | 32 vCPU | 256 GB RAM | 500 |
+| **PS-2700** | 48 vCPU | 128 GB RAM | 438 |
+| **PS-2800** | 64 vCPU | 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_.
{% callout %}
Cluster size options are capped at `PS-400` until you have a successfully paid $100 invoice. If you need larger sizes immediately, please [contact us](/contact) to unlock all sizes.
diff --git a/docs/reference/planetscale-system-limits.md b/docs/reference/planetscale-system-limits.md
index b3d9d2df..9b6ff4a9 100644
--- a/docs/reference/planetscale-system-limits.md
+++ b/docs/reference/planetscale-system-limits.md
@@ -1,7 +1,7 @@
---
title: 'PlanetScale system limits'
subtitle: 'Learn about system limits that PlanetScale puts in place to protect your database.'
-date: '2024-04-26'
+date: '2024-07-12'
---
## Table limits
@@ -14,6 +14,24 @@ Individual tables are limited to a maximum of `1017` columns each.
Database client connections that are held open longer than `24 hours` may be terminated unexpectedly. We recommend that long running database connections are closed and reconnected at least once per day.
+## Simultaneous transaction limits
+
+Each database has a limit on the number of simultaneous _transactions_ it can process, also known as the _transaction pool_.
+If you exceed the _transaction pool_ setting for your database, you may encounter this error:
+
+```
+vttablet: rpc error: code = ResourceExhausted desc = transaction pool connection limit exceeded
+```
+
+This often can be mitigated by trying the one of the following solutions:
+
+A) Reduce the amount of parallelism in the requests being sent to the database.
+B) Shorten lengthy transactions by reducing batch sizes or making some other application-level adjustment.
+
+If you cannot make such changes to your application, consider choosing a larger instance type with a larger transaction pool.
+The exact limit varies depending on the instance type of your database.
+For details, see the [plans page](/docs/concepts/planetscale-plans).
+
## Query limits
PlanetScale has enforced some system limits to prevent long-running queries or transactions from: