diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-06-07 18:09:27 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-06-07 18:09:27 +0000 |
| commit | 5cda8c8a420399ca9687c4a981fefd50ce5a1fdd (patch) | |
| tree | 6050d7517a36798c9586e153df20a0696c5fcd4f /doc/administration/postgresql | |
| parent | 7bbc731c75d0b8bf7c74ba77d521266d2ed0a1fc (diff) | |
| download | gitlab-ce-5cda8c8a420399ca9687c4a981fefd50ce5a1fdd.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/postgresql')
| -rw-r--r-- | doc/administration/postgresql/pgbouncer.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/postgresql/pgbouncer.md b/doc/administration/postgresql/pgbouncer.md index 5a39565cef7..8ae2b6497f8 100644 --- a/doc/administration/postgresql/pgbouncer.md +++ b/doc/administration/postgresql/pgbouncer.md @@ -227,12 +227,12 @@ the database. Each of the listed services below use the following formula to def - `headroom` can be configured via `DB_POOL_HEADROOM` environment variable (default to `10`) To calculate the `default_pool_size`, multiply the number of instances of `puma`, `sidekiq` and `geo-logcursor` by the -number of connections each can consume as per listed above. The total will be the suggested `default_pool_size`. +number of connections each can consume as per listed above. The total is the suggested `default_pool_size`. If you are using more than one PgBouncer with an internal Load Balancer, you may be able to divide the `default_pool_size` by the number of instances to guarantee an evenly distributed load between them. -The `pgbouncer['max_client_conn']` is the hard-limit of connections PgBouncer can accept. It's unlikely you will need +The `pgbouncer['max_client_conn']` is the hard limit of connections PgBouncer can accept. It's unlikely you need to change this. If you are hitting that limit, you may want to consider adding additional PgBouncers with an internal Load Balancer. |