Hi Justin,
I have already checked running Postgres processes and strangely never
counted more than 20.
I'll check as you recommend on how ejabberd to postgresql connectivity
works. May be the answer lies there. Will get back if I find something.
Thanks for giving some direction to my thoughts.
Hi Dipanjan
If the connections are not being closed and left open , you should see
50,000 processes running on the server because postgresql creates/forks a
new process for each connection
Just having that many processes running will exhaust resources, I would
confirm that the process are stil
Thanks Michael for the recommendation and clarification.
Will try the with 32 MB on my next run.
BR,
Dipanjan
On Tue, Feb 25, 2020 at 10:51 PM Michael Lewis wrote:
> work_mem can be used many times per connection given it is per sort, hash,
> or other operations and as mentioned that can be mu
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
w
Hi Dipanjan
Please do not post to all the postgresql mailing list lets keep this on one
list at a time, Keep this on general list
Am i reading this correctly 10,000 to 50,000 open connections.
Postgresql really is not meant to serve that many open connections.
Due to design of Postgresql each c
Greetings,
I was trying to use postgresql database as a backend with Ejabberd XMPP
server for load test (Using TSUNG).
Noticed, while using Mnesia the “simultaneous users and open TCP/UDP
connections” graph in Tsung report is showing consistency, but while using
Postgres, we see drop in connect
