Re: Connection Pooling
| From: | Steven Roussey | Date: | Fri, 21 Jul 2000 18:23:06 +0000 |
| Subject: | Re: Connection Pooling | ||
| Groups: | php.general | ||
| Request: | Send a blank email to php-general+get-7612@lists.php.net to get a copy of this message | ||
-----------
Using pconnects() in PHP means that for every apache processes that is up,
we need to have an available connection to the DB server
-----------
This is indeed a big issue, but one (I think) that would best be solved
fixing PHP4. The connection pool on the web server should be 'per server'
not 'per apache' process.
This may not be a trivial effort (otherwise it would already be done -
right?!). I don't know if shared resources is available in Apache 1.3. I
can't imagine them leaving it out of Apache 2.0.
It is, however, likely the biggest downfall of using Apache/PHP4 on Linux
for any site that has grown to use multiple web servers connected to MySQL
on the backend. Or any other db I guess.
If you end up creating a proxy for pconnects that does its own connection
pooling, I'd be interested.
Also, does PHP4 work on any multi-threaded server on Linux? If we ditch
Apache and its process forking model, it might work more as expected. I'd
hate to move to Windows/IIS 5.0/PHP4, but it might fix this issue.
Please let me know what you discover.
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e