Re: Connections dropping while using Postgres backend DB with Ejabberd - Mailing list pgsql-general

From Michael Lewis
Subject Re: Connections dropping while using Postgres backend DB with Ejabberd
Date
Msg-id CAHOFxGrxvM1ZSPpSzX2DFQqqhLS9ea99LUB=-p_pnQPmAaKHPQ@mail.gmail.com
Whole thread Raw
In response to Re: Connections dropping while using Postgres backend DB with Ejabberd  (Justin <zzzzz.graf@gmail.com>)
Responses Re: Connections dropping while using Postgres backend DB with Ejabberd  (Dipanjan Ganguly <dipagnjan@gmail.com>)
List pgsql-general
work_mem can be used many times per connection given it is per sort, hash, or other operations and as mentioned that can be multiplied if the query is handled with parallel workers. I am guessing the server has 16GB memory total given shared_buffers and effective_cache_size, and a more reasonable work_mem setting might be on the order of 32-64MB.

Depending on the type of work being done and how quickly the application releases the db connection once it is done, max connections might be on the order of 4-20x the number of cores I would expect. If more simultaneous users need to be serviced, a connection pooler like pgbouncer or pgpool will allow those connections to be re-used quickly.

These numbers are generalizations based on my experience. Others with more experience may have different configurations to recommend.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Trigger
Next
From: Mani Sankar
Date:
Subject: Re: LDAP with TLS is taking more time in Postgresql 11.5