Re: [PHP4BETA] Database Connection Pooling

> If that is what it was meant, I don't think it is a good idea. One > persistent connection per process is better than have Apache processes > competing for database connections allocated from a common pool. The way I > see it, that would impose needless latency in database connections. ---I disagree. For running 1 web server for a site, it's probably just fine to have 1 persistent connection per apache process. But in my case, my web site is actually multiple machines that are behind a local director. I only have 1 database, so having 1 persistent connection for each apache process is murder. n boxes * 64 apache process = a LOT of persistent connections. So if you had the ability to multiplex your persistent connections on 1 machine, then the overhead is desired in this case. So you could allocate (for example) 10 persistent connections per machine. So having 20 web servers is doable. Walt