shishantbiswas/coder
1
0
Fork 0
mirror of https://github.com/coder/coder.git synced 2026-06-02 20:48:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify max_connections implications (#21596)

Browse Source 
Signed-off-by: Danny Kopping <danny@coder.com>
This commit is contained in:
Danny Kopping
2026-01-21 22:10:12 +02:00
committed by GitHub
parent 47b3846bca
commit 1dd0519a38
1 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tutorials/best-practices/scale-coder.md
+11 -5
View File
@@ -221,13 +221,19 @@ give specific sizing recommendations for various user scales.
### Connection pool tuning
Coder Server maintains a pool of connections to PostgreSQL. You can tune the
pool size with these settings:
pool size with the following settings:
> [!NOTE]
> When adjusting these settings, please ensure that your PostgreSQL Server has `max_connections`
> set appropriately to accommodate all Coder Server replicas multiplied by the
> maximum number of open connections. We recommend configuring an additional 20%
> of connections to account for churn and other clients.
>
> Also note that increasing `max_connections` will result in potentially higher
> CPU and RAM usage, so you'll need to monitor accordingly.
- `--postgres-conn-max-open` (env: `CODER_PG_CONN_MAX_OPEN`): Maximum number of open
connections. Default: 10. Ensure that your PostgreSQL Server has `max_connections`
set appropriately to accommodate all Coder Server replicas multiplied by the
maximum number of open connections. We recommend configuring an additional 20%
of connections to account for churn and other clients.
connections. Default: 10.
- `--postgres-conn-max-idle` (env: `CODER_PG_CONN_MAX_IDLE`): Maximum number of idle
connections kept in the pool. Default: "auto", which uses max open / 3.