#25552 [Opn->Bgs]: Documentation unclear about persistent database connections
| From: | irchtml@php.net | Date: | Thu, 08 Apr 2004 05:41:22 +0000 |
| Subject: | #25552 [Opn->Bgs]: Documentation unclear about persistent database connections | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969359976@lists.php.net to get a copy of this message | ||
ID: 25552
Updated by: irchtml@php.net
Reported By: grange at club-internet dot fr
-Status: Open
+Status: Bogus
Bug Type: Documentation problem
PHP Version: Irrelevant
New Comment:
Quote from the manual:
They cause the child process to simply connect only once for its entire
lifespan, instead of every time it processes a page that requires
connecting to the SQL server. This means that for every child that
opened a persistent connection will have its own open persistent
connection to the server. For example, if you had 20 different child
processes that ran a script that made a persistent connection to your
SQL server, you'd have 20 different connections to the SQL server, one
from each child.
---
Each child would have it's own connection, so the latter case in your
report would be true. Hope that clears it up. If you have any further
suggestions please feel free to e-mail phpdoc@lists.php.net. Thank
you!
Previous Comments:
------------------------------------------------------------------------
[2003-09-15 17:44:07] grange at club-internet dot fr
Description:
------------
Hello,
The documentation about persistent db connections (ie. chapter 21 of
the manual) should probably be more clear whether connections are
persistent across *subsequent http requests served by different apache
child processes* or persistent across *subsequent http requests served
by the same child process* (or is it none if the above... oh well 8-)).
The french translation clearly states the first, while as I'm reading
the english documentation (and the first user contributed note), I
understand the oci8 extension (as well as other extensions providing
persistent connections) behaves the second way.
Theorically, in the second case, the number of db connections should
increase to MaxClients, where in the first case, (ignoring peak
activity) it should be less, depending on the percentage of db-driven
pages out of static pages (ie for 5% of db pages, 5% of MaxClients).
Anyway, thanks for the great work !
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=25552&edit=1