From: Kevin Grittner <kgrittn@ymail.com>
To: Igor Neyman <ineyman@perceptron.com>
To: Viktor <viktor@okservers.eu>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Random server overload
Date: Wed, 2 Oct 2013 07:58:45 -0700 (PDT)
Message-ID: <1380725925.87939.YahooMailNeo@web162906.mail.bf1.yahoo.com> (raw)
In-Reply-To: <A76B25F2823E954C9E45E32FA49D70EC4282408F@mail.corp.perceptron.com>
References: <524ACBD0.5000400@okservers.eu>
<A76B25F2823E954C9E45E32FA49D70EC42823C34@mail.corp.perceptron.com>
<524BD56C.7030900@okservers.eu>
<A76B25F2823E954C9E45E32FA49D70EC4282408F@mail.corp.perceptron.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Igor Neyman <ineyman@perceptron.com> wrote:
>> Our Java application uses c3p0 connection pooler and we don't
>> think that it's the issue.
>
> "Client-side" connection pooling is different from server-side
> (such as PgBouncer), and I believe is not as effective as
> PgBouncer.
In my experience a good client-side pooler can be more effective --
if all significant traffic is going through a single pooler and the
pool size is set appropriately. For example, we improved
performance on a 16 code 256 GB server by reducing the pool size of
the web application (handling hundreds of requests per second from
3000 concurrent users) from a maximum of 60 database connections to
35.
http://wiki.postgresql.org/wiki/Number_Of_Database_Connections> As you stated in original message you have multiple idle
> connections, that's waste of resources.
... and a risk that if they all become active at one time, you can
have a seemingly-random server overload.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: kgrittn@ymail.com, ineyman@perceptron.com, viktor@okservers.eu
Subject: Re: Random server overload
In-Reply-To: <1380725925.87939.YahooMailNeo@web162906.mail.bf1.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox