[PERFORM] 100 simultaneous connections, critical limit?

2004-01-16 Thread Jón Ragnarsson
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-t

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-15 Thread Thomas Swan
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 ofte

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Andrew McMillan
On Thu, 2004-01-15 at 01:48, 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? Sh

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Christopher Kings-Lynne
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 Turck

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread scott.marlowe
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 solve

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Evil Azrael
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 persista

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Adam Alkins
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. I share the above view. I've had little success with p

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread scott.marlowe
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

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Tom Lane
Christopher Browne <[EMAIL PROTECTED]> writes: > Clinging to sanity, [EMAIL PROTECTED] (Jón Ragnarsson) mumbled into her beard: >> Then I read somewhere that Postgres only supports 100 simultaneous >> connections (default). > I thought the out-of-the-box default was 32. Pre-7.4 it was 32; in 7.4

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Nick Barr
> -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, connecti

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Jón Ragnarsson
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 wro

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Christopher Browne
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 (defaul

Re: [PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Shridhar Daithankar
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 limitat

[PERFORM] 100 simultaneous connections, critical limit?

2004-01-14 Thread Jón Ragnarsson
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-tra