From: Jón Ragnarsson <jonr@physicallink.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 100 simultaneous connections, critical limit?
Date: Wed, 14 Jan 2004 13:44:17 +0000
Message-ID: <400547B1.7000202@physicallink.com> (raw)
In-Reply-To: <m3fzeilkyg.fsf@wolfe.cbbrowne.com>
References: <40053A91.5060001@physicallink.com>
<m3fzeilkyg.fsf@wolfe.cbbrowne.com>
Ok, connection pooling was the thing that I thought of first, but I
haven't found any docs regarding pooling with PHP+Postgres.
OTOH, I designed the application to be as independent from the DB as
possible. (No stored procedures or other Postgres specific stuff)
Thanks,
J.
Christopher Browne wrote:
> Clinging to sanity, jonr@physicallink.com (Jón Ragnarsson) mumbled into her beard:
>
>>I am writing a website that will probably have some traffic.
>>Right now I wrap every .php page in pg_connect() and pg_close().
>>Then I read somewhere that Postgres only supports 100 simultaneous
>>connections (default). Is that a limitation? Should I use some other
>>method when writing code for high-traffic website?
>
>
> I thought the out-of-the-box default was 32.
>
> If you honestly need a LOT of connections, you can configure the
> database to support more. I "upped the limit" on one system to have
> 512 the other week; certainly supportable, if you have the RAM for it.
>
> It is, however, quite likely that the connect()/close() cuts down on
> the efficiency of your application. If PHP supports some form of
> "connection pooling," you should consider using that, as it will cut
> down _dramatically_ on the amount of work done establishing/closing
> connections, and should let your apps use somewhat fewer connections
> more effectively.
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-performance@postgresql.org
Cc: jonr@physicallink.com
Subject: Re: 100 simultaneous connections, critical limit?
In-Reply-To: <400547B1.7000202@physicallink.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