scott.marlowe wrote:
On Wed, 14 Jan 2004, Adam Alkins wrote:
scott.marlowe wrote:
A few tips from an old PHP/Apache/Postgresql developer.
1: Avoid pg_pconnect unless you are certain you have load tested the
system and it will behave properly. pg_pconnect often creates as many
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
On Wednesday 14 January 2004 18:18, Jón Ragnarsson wrote:
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
Clinging to sanity, [EMAIL PROTECTED] (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).
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
-Original Message-
From: [EMAIL PROTECTED]
[mailto:pgsql-performance-
[EMAIL PROTECTED] On Behalf Of Jón Ragnarsson
Sent: 14 January 2004 13:44
Cc: [EMAIL PROTECTED]
Subject: Re: [PERFORM] 100 simultaneous connections, critical limit?
Ok, connection pooling was the thing that I
On Wed, 14 Jan 2004, Jón Ragnarsson wrote:
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
Hi!
AA scott.marlowe wrote:
A few tips from an old PHP/Apache/Postgresql developer.
1: Avoid pg_pconnect unless you are certain you have load tested the
system and it will behave properly. pg_pconnect often creates as many
issues as it solves.
My experience with persistant connections
On Wed, 14 Jan 2004, Adam Alkins wrote:
scott.marlowe wrote:
A few tips from an old PHP/Apache/Postgresql developer.
1: Avoid pg_pconnect unless you are certain you have load tested the
system and it will behave properly. pg_pconnect often creates as many
issues as it solves.
7: Profile your machine under parallel load. Note that machine simos
(i.e. the kind you get from the ab utility) generally represent about 10
to 20 real people. I.e. if your machine runs well with 20 machine simos,
you can bet on it handling 100 or more real people with ease.
8. Use the
On Thu, 2004-01-15 at 01:48, Jn Ragnarsson wrote:
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
11 matches
Mail list logo
