docs: add limits page #4316
docs: add limits page #4316
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
content/docs/reference/limits.md
Outdated
|
|
||
| This page provides a comprehensive reference of all limits in the Neon platform, organized by category. Limits vary by [Neon plan](/docs/introduction/plans) unless otherwise noted. For [Agent plan](/docs/introduction/agent-plan) specific limits, see the [Agent plan limits](#agent-plan-limits) section. | ||
|
|
||
| <Admonition type="tip"> |
There was a problem hiding this comment.
Let's leave this out to avoid creating support requests.
content/docs/reference/limits.md
Outdated
| | Autoscaling max | 2 CU (8 GB RAM) | 16 CU (64 GB RAM) | 16 CU (64 GB RAM) | - | | ||
| | Fixed compute max | - | - | 56 CU (224 GB RAM) | Scale plan only | | ||
| | Compute hours | 100 CU-hours/project/month | Usage-based | Usage-based | Free plan limit resets monthly | | ||
| | Non-default branch compute | 5 hours/month | - | - | Free plan only; default branch exempt | |
There was a problem hiding this comment.
This 5 hour limit is the legacy limit, so it doesn't apply
There was a problem hiding this comment.
@danieltprice Remove info from here? https://neon.com/docs/manage/branches#non-default-branch
content/docs/reference/limits.md
Outdated
| | 8 | 32 | 3,357 | | ||
| | 9–56 | 36–224 | 4,000 | | ||
|
|
||
| <Admonition type="note"> |
There was a problem hiding this comment.
That's the formula for compute size in an autoscaling config. Please see the link for the rest of the formula (I updated it recently).
| Seven connections are reserved for Neon's internal `superuser` account. For autoscaling configurations, `max_connections` is calculated based on the formula: `min(max_compute_size, 8 × min_compute_size)`. See [Parameter settings that differ by compute size](/docs/reference/compatibility#parameter-settings-that-differ-by-compute-size) for details. | ||
| </Admonition> | ||
|
|
||
| For more information, see [Connection pooling](/docs/connect/connection-pooling). |
There was a problem hiding this comment.
I think it's important here to mention more explcitly that we support up to 10000 concurrent connections with a pooled connection string.
content/docs/reference/limits.md
Outdated
|
|
||
| | Limit | Free | Paid Plans | Notes | | ||
| | :------------------------ | :--- | :--------- | :--------------------------------- | | ||
| | Read replicas per project | 3 | - | Each replica is a separate compute | |
There was a problem hiding this comment.
A dash here is no limit, but above a dash for protect branches means N/A, so we'll need to be more explicit I think by using "N/A" or "No limit" or something like that
| For more information, see [Neon Auth](/docs/auth/overview). | ||
|
|
||
| ## Query and request size limits | ||
|
|
There was a problem hiding this comment.
We should be explcit that this is a Neon serverless driver limit
|
|
||
| For more information, see [Neon serverless driver](/docs/serverless/serverless-driver). | ||
|
|
||
| ## Configurable quotas |
There was a problem hiding this comment.
Not sure this fits. It's a user defined limit in a specific use case. Maybe don't include it.
|
|
||
| --- | ||
|
|
||
| ## Agent plan limits |
There was a problem hiding this comment.
I think this might be out of scope, maybe just point to the agent plan instead
Co-authored-by: Daniel <10074684+danieltprice@users.noreply.github.com>
Thanks! Co-authored-by: Daniel <10074684+danieltprice@users.noreply.github.com>
| @@ -0,0 +1,154 @@ | |||
| --- | |||
| title: Usage limits | |||
There was a problem hiding this comment.
Let's change the title to "Platform limits" to avoid confusion with billing usage and add the page here:
https://neon.com/docs/manage/platform
Maybe as a "Platform limits" topic under "Projects & resources"?
3 participants
Drafted a centralized page for usage limits. Setting to DRAFT, needs more review/research.