docs: compute size updates

neondatabase · Dec 11, 2024 · ca643c1 · ca643c1
1 parent 2de6cbc
commit ca643c1
Show file tree

Hide file tree

Showing 6 changed files with 36 additions and 21 deletions.
diff --git a/content/docs/get-started-with-neon/production-checklist.md b/content/docs/get-started-with-neon/production-checklist.md
@@ -43,7 +43,7 @@ In Neon, your compute size determines the amount of vCPU and memory your databas
 - **Free Plan**: Starting at a fixed 0.25 CU (0.25 vCPU, 1 GB RAM), up to 2 CU (2 vCPU, 8 GRM RAM) with autoscaling enabled
 - **Launch**: Up to 4 CUs (4 vCPU, 16 GB RAM)
 - **Scale**: Up to 8 CUs (8 vCPU, 32 GB RAM)
-- **Business**: Up to 10 CUs (10 vCPU, 40 GB RAM)
+- **Business**: Up to 56 CUs (56 vCPU, 64 GB RAM)
 - **Enterprise**: Larger sizes
 
 You should start with a compute size that can hold your data or at least your most frequently accessed data (your [working set](/docs/reference/glossary#working-set)) in memory. If you are using Neon's _Autoscaling_ feature, we recommend the same for your **minimum compute size** setting (see [Configure Autoscaling](#configure-autoscaling)).

diff --git a/content/docs/guides/autoscaling-guide.md b/content/docs/guides/autoscaling-guide.md
@@ -35,7 +35,7 @@ To edit a compute:
 1. On the **Edit compute** settings drawer, toggle **Enable autoscaling** to enable it and use the slider to specify a minimum and maximum compute size.
    ![Autoscaling edit settings](/docs/introduction/autoscaling_config.png)
 
-   Neon scales the compute size up and down within the specified range to meet workload demand. Autoscaling currently supports a range of 1/4 (.25) to 10 vCPUs. One vCPU has 4 GB of RAM, 2 vCPUs have 8 GB of RAM, and so on. The amount of RAM in GB is always 4 times the number of vCPUs. For an overview of available compute sizes, see [Compute size and autoscaling configuration](/docs/manage/endpoints#compute-size-and-autoscaling-configuration).
+   Neon scales the compute size up and down within the specified range to meet workload demand. Autoscaling currently supports a range of 1/4 (.25) to 16 vCPUs. One vCPU has 4 GB of RAM, 2 vCPUs have 8 GB of RAM, and so on. The amount of RAM in GB is always 4 times the number of vCPUs. For an overview of available compute sizes, see [Compute size and autoscaling configuration](/docs/manage/endpoints#compute-size-and-autoscaling-configuration).
 
    <Admonition type="note">
    You can configure the scale to zero setting for your compute at the same time. The scale to zero setting defines the period of inactivity after which a compute is automatically suspended. For more, see [Scale to Zero](/docs/introduction/scale-to-zero).

diff --git a/content/docs/guides/vercel-native-integration.md b/content/docs/guides/vercel-native-integration.md
@@ -58,7 +58,7 @@ To install the **Neon Postgres Native Integration** from the Vercel Marketplace:
    | Free     | 0.25 - 2 vCPUs  | 5 minutes (Default)                                      |
    | Launch   | 0.25 - 4 vCPUs  | 5 minutes or more (Default, Never, Custom)               |
    | Scale    | 0.25 - 8 vCPUs  | 1 minute or more (Default, Never, Custom)                |
-   | Business | 0.25 - 10 vCPUs | 1 minute or more (Default, Never, Custom)                |
+   | Business | 0.25 - 56 vCPUs | 1 minute or more (Default, Never, Custom)                |
 
    For an overview of what comes with each Neon Plan, please refer to the Neon [Pricing](https://neon.tech/pricing) page.
    </Admonition>

diff --git a/content/docs/introduction/plans.md b/content/docs/introduction/plans.md
@@ -184,7 +184,7 @@ Business plan users have access to [extra compute, storage, and projects](/docs/
 
 ### Business plan features
 
-- Autoscaling compute up to 10 vCPUs and 40 GB RAM
+- Autoscaling compute up to 16 vCPUs and 40 GB RAM
 - Monitoring with 14 days of historical data
 - Advanced Postgres features, including connection pooling, logical replication, and 60+ Postgres extensions
 - Neon features such as branching, point-in-time restore up to **30 days** in the past, time travel connections, and more

diff --git a/content/docs/manage/endpoints.md b/content/docs/manage/endpoints.md
@@ -118,6 +118,10 @@ The Postgres `max_connections` setting defines your compute's maximum simultaneo
 
 The following table outlines the vCPU, RAM, LFC size (80% of RAM), and the `max_connections` limit for each compute size that Neon supports.
 
+<Admonition type="note">
+Compute size support differs by [Neon plan](https://neon.tech/docs/introduction/plans). Autoscaling is supported up to 16 CU. Neon supports fixed compute sizes (no autoscaling) for computes sizes larger than 16 CU.
+</Admonition>
+
 | Min. Compute Size (CU) | vCPU | RAM   | LFC size | max_connections |
 | ---------------------- | ---- | ----- | -------- | --------------- |
 | 0.25                   | 0.25 | 1 GB  | 0.8 GB   | 112             |
@@ -132,6 +136,32 @@ The following table outlines the vCPU, RAM, LFC size (80% of RAM), and the `max_
 | 8                      | 8    | 32 GB | 25.6 GB  | 3604            |
 | 9                      | 9    | 36 GB | 28.8 GB  | 4000            |
 | 10                     | 10   | 40 GB | 32 GB    | 4000            |
+| 11                     | 11   | 44 GB | 35.2 GB  | 4000            |
+| 12                     | 12   | 48 GB | 38.4 GB  | 4000            |
+| 13                     | 13   | 52 GB | 41.6 GB  | 4000            |
+| 14                     | 14   | 56 GB | 44.8 GB  | 4000            |
+| 15                     | 15   | 60 GB | 48 GB    | 4000            |
+| 16                     | 16   | 64 GB | 51.2 GB  | 4000            |
+| 18                     | 18   | 72 GB | 57.6 GB  | 4000            |
+| 20                     | 20   | 80 GB | 64 GB    | 4000            |
+| 22                     | 22   | 88 GB | 70.4 GB  | 4000            |
+| 24                     | 24   | 96 GB | 76.8 GB  | 4000            |
+| 26                     | 26   | 104 GB| 83.2 GB  | 4000            |
+| 28                     | 28   | 112 GB| 89.6 GB  | 4000            |
+| 30                     | 30   | 120 GB| 96 GB    | 4000            |
+| 32                     | 32   | 128 GB| 102.4 GB | 4000            |
+| 34                     | 34   | 136 GB| 108.8 GB | 4000            |
+| 36                     | 36   | 144 GB| 115.2 GB | 4000            |
+| 38                     | 38   | 152 GB| 121.6 GB | 4000            |
+| 40                     | 40   | 160 GB| 128 GB   | 4000            |
+| 42                     | 42   | 168 GB| 134.4 GB | 4000            |
+| 44                     | 44   | 176 GB| 140.8 GB | 4000            |
+| 46                     | 46   | 184 GB| 147.2 GB | 4000            |
+| 48                     | 48   | 192 GB| 153.6 GB | 4000            |
+| 50                     | 50   | 200 GB| 160 GB   | 4000            |
+| 52                     | 52   | 208 GB| 166.4 GB | 4000            |
+| 54                     | 54   | 216 GB| 172.8 GB | 4000            |
+| 56                     | 56   | 224 GB| 179.2 GB | 4000            |
 
 When selecting a compute size, ideally, you want to keep as much of your dataset in memory as possible. This improves performance by reducing the amount of reads from storage. If your dataset is not too large, select a compute size that will hold the entire dataset in memory. For larger datasets that cannot be fully held in memory, select a compute size that can hold your [working set](/docs/reference/glossary#working-set). Selecting a compute size for a working set involves advanced steps, which are outlined below. See [Sizing your compute based on the working set](#sizing-your-compute-based-on-the-working-set).
 

diff --git a/content/docs/reference/glossary.md b/content/docs/reference/glossary.md
@@ -115,26 +115,11 @@ The access point through which users connect to a Neon compute. In the context o
 
 ## compute size
 
-The Compute Units (CU) that are allocated to a Neon compute. A Neon compute can have anywhere from .25 to 10 CU. The number of units determines the processing capacity of the compute.
+The Compute Units (CU) that are allocated to a Neon compute. A Neon compute can have anywhere from .25 to 56 CU. The number of units determines the processing capacity of the compute.
 
 ## Compute Unit (CU)
 
-A unit that measures the processing power or "size" of a Neon compute. A Compute Unit (CU) includes vCPU and RAM. A Neon compute can have anywhere from .25 to 10 CUs. The following table shows the vCPU and RAM for each CU:
-
-| Compute Unit (CU) | vCPU | RAM   |
-| :---------------- | :--- | :---- |
-| .25               | .25  | 1 GB  |
-| .5                | .5   | 2 GB  |
-| 1                 | 1    | 4 GB  |
-| 2                 | 2    | 8 GB  |
-| 3                 | 3    | 12 GB |
-| 4                 | 4    | 16 GB |
-| 5                 | 5    | 20 GB |
-| 6                 | 6    | 24 GB |
-| 7                 | 7    | 28 GB |
-| 8                 | 8    | 32 GB |
-| 9                 | 9    | 36 GB |
-| 10                | 10   | 40 GB |
+A unit that measures the processing power or "size" of a Neon compute. A Compute Unit (CU) includes vCPU and RAM. A Neon compute can have anywhere from .25 to 56 CUs. See [Compute size and autoscaling configuration](/docs/manage/endpoints#compute-size-and-autoscaling-configuration).
 
 ## compute hours