Re: Large PHP/Database driven site & scalability
| From: | Michael Kimsal | Date: | Wed, 19 Jul 2000 16:49:50 +0000 |
| Subject: | Re: Large PHP/Database driven site & scalability | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-7308@lists.php.net to get a copy of this message | ||
Hello again Eric,
This is something we go back and forth on here. I'm not sure
why you want connection pooling. As I wrote before, it is
something we've looked in to, but as we discuss it, one thing
keeps coming up: any pooling mechanism is going to
reduce efficiency. The only benefit I see to it is handling errors
if/when there are more PHP connections than MySQL available
connections. Have you modified MySQL to be able to handle
>500 concurrent connections?
The Perl stuff we looked at was initially for Perl code, and we
were trying to get it to deal with PHP, but we don't know
enough about the PHP internals to interface properly. Again,
I suspect this would take some custom module writing, a bit
beyond our capabilities at this point in time.
Can you let me know what benefits you are looking for with
pooling? There may be something I've overlooked. The other
benefit is keeping yourself in line with licensing, of course
(limit pool to max of 50 connections if your DB is licensed for
max of 50, but MySQL doesn't have that licensing limitation, does it?)
--
==========================
Michael Kimsal
http://www.tapinternet.com
734-480-9961