Re: [phplib] Problem with permanent connections? From: fabrizio.ermini <email protected>
Date: 07/08/00

> The subject of "too many connections" has been tossed around here and on
> the PHP lists several times in the past year, and I have missed it if
> anyone has come up with an explanation ...
>

For what I've been able to ascertain up now (thanks Cameron!), that
problem is that when the "master" apache process reaps child
processes that have reached the end of their lifespan (depending
on various factors like MaxRequestForChild and the like) backend
processes opened by said child processes are NOT closed but
remain there, doing nothing but wasting memory and IPC
resources. I guess this is a problem relating to the Php module,
that doesn't do a correct clean-up when is sig-killed.

> The only fact of which I'm sure is that, as soon as I changed PHPLib's
> "p_connect" to "connect", the problem disappeared. This experience has
> held true on several different hosts around the country for both virtual
> and dedicated clients, for SCO and RH and FreeBSD, for heavy-load sites
> and ego sites ...
>

Yes, I'd follow this hint. Moreover, Cameron here was reporting to
me that there is really not so much of a difference, in terms of
speed, when choosing normal connect instead that pconnect under
heavy use.

Anybody has some other contribution on this thread?
IMVVVVVHO, this is an important issue. If pconnect gives this
pain, maybe Kristian could consider using the usual connect for
pg_sql?

TIA,
hear you soon

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Fabrizio Ermini Alternate E-mail:
C.so Umberto, 7 faermini <email protected>
loc. Meleto Valdarno Mail on GSM: (keep it short!)
52020 Cavriglia (AR) faermini <email protected>

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>