[OGo-Users] postgres connection limit exceeded
Adam Tauno Williams
users@opengroupware.org
Fri, 29 Feb 2008 14:01:13 -0500
> > > as the company grows, more and more people are using ogo. From time to
> > > it happens that people that try to login, get an error message, ogo
> > > reach its database. Users with an already active session, can still
> > > figured out, that the postgres database had its connection limit
> > > Raising the connection limit fixes the problem for a while, but I don't
> > > think that this is the best idea, if good at all.
> > What did you raise it too? The defaults in PostgreSQL are so low it is
> > silly, so unless you raised them ALLOT I wouldn't be concerned.
> right now, I doubled the default value from 100 to 200. Not sure to what
> values I can raise it until I run into trouble.
Higher than that. Just my network management system (OpenNMS) runs at
384 connections. And that is a crufty old PostgreSQL 8.0.
My production PostgreSQL server has a max connections settings of 512.
What you want to really avoid is many concurrently active sessions, that
will kill you. Idle connections don't cost much until you have *lots*
of them.
> > > Well, after googling for a solution to the problem, the recommended
> answer
> > > is either fix the application, or use a connection pooling daemon like
> > > pgbouncer.
> > Depends on how many connections we are talking about?
> above mentioned connections, 100 was not enough, there the problems
> happened. Well, as long as I can raise the connection limit without noticing
> problems I'm fine, and do not need pgbouncer.
> > > Is there an ogo default, allowing me to kill idle database sessions
> > The old XML-RPC daemon can leak connections. I haven't see that with
> > ZideStore or OGo.
> > http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1884
> ah, interesting.
WebUI opens one per session, and they are cached so they linger for a
time after the user closes the browser. ZideStore seems to open one per
user and reuse that for future requests by the user. Both WebUI and
ZideStore also have an overhead of one connection.