Skip to content

NOJIRA-99: Update docs for hyperdrive conn limits #19459

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 28, 2025
Merged

NOJIRA-99: Update docs for hyperdrive conn limits #19459

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions src/content/docs/hyperdrive/platform/limits.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,21 +17,18 @@ The following limits apply to Hyperdrive configuration, connections, and queries
| Maximum query (statement) duration | 60 seconds |
| Maximum username length | 63 characters (bytes) [^1] |
| Maximum database name length | 63 characters (bytes) [^1] |
| Maximum origin database connections per region | 10-20 |
| Maximum potential origin database connections | 10 \* number of regions serving traffic (approx. \~80 - 100 connections) [^2] |
| Maximum potential origin database connections | approx. \~100 connections [^2] |

:::note

Hyperdrive does not have a hard limit on the number of concurrent *client* connections made from your Workers.

As many hosted databases have limits on the number of unique connections they can manage, Hyperdrive attempts to keep number of concurrent pooled connections to your origin database lower.

:::

[^1]: This is a limit enforced by PostgreSQL. Some database providers may enforce smaller limits.

[^2]: Hyperdrive maintains semi-regional connection pools to balance between latency, reliability and overall load on your origin database.
[^2]: Hyperdrive is a distributed system, so it is possible for a client to be unable to reach an existing pool. In this scenario, a new pool will be established, with its own allocation of connections. This favors availability over strictly enforcing limits, but does mean that it is possible in edge cases to overshoot the normal connection limit.

:::note
You can request adjustments to limits that conflict with your project goals by contacting Cloudflare. Not all limits can be increased. To request an increase, submit a [Limit Increase Request](https://forms.gle/ukpeZVLWLnKeixDu7) and we will contact you with next steps.
:::
:::
Loading