I found a record of developers explaining that mysql_pconnect caused
more problems than it solved, and thus they didn't include it in the
mysqli interface. Moving from mysql_connect to mysql_pconnect fixed
some serious performance issues in our systems, and I'd like to
understand how to be sure that we can migrate to mysqli prior to doing

I searched the archives of this newsgroup and found only one message
about this, and that unanswered.

mysql_pconnect maintains persistent connections to a database across
successive requests when used within the module version of php; thus
eliminating the cost of re-establishing connections for each new

if i have a web server serving thousands of requests per minute,
creating and destroying thousands of database connections per minutes
seems to have the effect of pouring diesel into the drive bay on our
webserver and tossing in a match.

does mysqli_connect offer some facility for mitigating the cost of
connections under the hood, or is it only designed for lower volume
servers? or is there some other way of caching a db_link across
multiple requests that I am not aware of?


Work as though you live in the younger days of a better nation!
---------------------------------------------- -- Alasdair Gray

PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to