Re: re : PHP and persistent connections

From: GH <grasshacker(at)over-yonder(dot)net>
To:
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: re : PHP and persistent connections
Date: 2000-11-23 16:14:17
Message-ID: 20001123101417.C30801@over-yonder.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Thu, Nov 23, 2000 at 04:53:35PM +0100, some SMTP stream spewed forth:
> Set the number of connection in php.ini to 2

I tried doing this, with the max set to 1, 2, and 3; but the number
of backends continues to grow until smacking into the ceiling.
What is controlled by max_persistent? It seems like PHP is just
ignoring this value. I apologize for bringing PHP onto this list, but
it is relevant.

Should not the backends die at *some* point?

Using regular connections almost triples the script's execution time.
(It is still under .5 seconds, but...)

It seems like the number of Apache processes would have to be *really*
low or the number of backends would have to be *really* high.

Our backend limit is still the default 32.

I thank you.
gh

>
> Exemple :
> [PostgresSQL]
> pgsql.allow_persistent = On ; allow or prevent persistent link
> pgsql.max_persistent = 2 ; maximum number of persistent links. -1
> means no limit
> pgsql.max_links = 2 ; maximum number of links (persi
> stent+non persistent). -1 means no limit
>
> Because if you keep the default value each apache process
> has an ulimited number of connection. So if your
> httpd start with 10 child process you have 20 persistent connections. So be carefull about the number of apache
> process and check the value of persistent connection
> in php.ini in order to adjust it.
>
> Cheers
>
> PEJAC Pascal
>
>

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message GH 2000-11-23 19:21:40 Re: re : PHP and persistent connections
Previous Message pejac 2000-11-23 15:53:35 re : PHP and persistent connections