| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Justin <zzzzz(dot)graf(at)gmail(dot)com> |
| Cc: | Chris Ellis <chris(at)intrbiz(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: sensible configuration of max_connections |
| Date: | 2020-02-07 18:06:33 |
| Message-ID: | CAHOFxGpni9Mx8XnDTebNC3+H3brK958WpecZxqFAmCzWFe8DXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Feb 7, 2020 at 6:29 AM Justin <zzzzz(dot)graf(at)gmail(dot)com> wrote:
> WorkMem is the biggest consumer of resources lets say its set to 5 megs
> per connection at 1000 connections that 5,000 megs that can be allocated.
>
Clarification- work_mem is used per operation (sort, hash, etc) and could
be many many times with a complicated query, and/or parallel processing
enabled. It could be that a single connection uses 10x work_mem or more.
https://www.postgresql.org/docs/current/runtime-config-resource.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Gendler | 2020-02-07 18:56:20 | Re: Fwd: sensible configuration of max_connections |
| Previous Message | Kasun Kulathunga | 2020-02-07 16:52:27 | Re: POLL: Adding transaction status to default psql prompt |