Connection pooling vs persist connection mysqli
| From: | dhruv kapatel | Date: | Thu, 24 Jul 2014 05:11:38 +0000 |
| Subject: | Connection pooling vs persist connection mysqli | ||
| Groups: | php.webmaster | ||
| Request: | Send a blank email to php-webmaster+get-19507@lists.php.net to get a copy of this message | ||
I've read that mysqli introduced connection pooling that was not available
in mysql.http://php.net/manual/en/mysqli.quickstart.connections.php
I've read this question
<http://stackoverflow.com/questions/9736188/mysql-persistent-connection-vs-connection-pooling>
that
explains the difference between connection pooling and persist connections.
In the mysqli documentation for Persistent connection
<http://php.net/manual/en/mysqli.quickstart.connections.php>
they have
written that:
If a unused persistent connection for a given combination of host,
username, password, socket, port and default database can not be found in
the connection pool, then mysqli opens a new connection.
So, does mysqli use connection pooling for persistent connections?
If yes, then what is difference between connection pooling and persistent
connections in mysqli?
If no, then how does mysqli perform a lookup for a connection object for a
persistent connection?
--
*With Regards:Kapatel Dhruv vmobile:+919909214243*
<https://www.facebook.com/kapateldhruv>
<https://twitter.com/kapatel_dhruv>
<http://in.linkedin.com/pub/dhruv-kapatel/28/938/734>
<https://plus.google.com/u/0/107663824071419377609/posts>
<http://stackoverflow.com/users/2016271/dhruv>