Question

I’m implementing an application that will have a lot of clients querying lots of small data packages from my webserver. Now I’m unsure whether to use persistent data connections to the database or not. The database is currently on the same system as the webserver and could connect via the socket, but this may change in the near future.

As I know a few releases of PHP ago mysqli_pconnect was removed because it behaved suboptimally. In the meantime it seems to be back again.

Based on my scenario I suppose I won’t have an other chance to handle thousands of queries per minute but with loads of persistent connections and a MySQL configuration that reserves only little resources per connection, right?

Thanks for your input!

Answer 1

What happened when you tested it?

With the nest will in the world, there’s no practical way you can convey all the informaton required for people to provide a definitive answer in a SO response. However usually there is very little overhead in establishing a mysql connection, particularly if it resides on the same system as the database client (in this case the webserver). There’s even less overhead if you use a filesystem rather than a network socket.

So I’d suggest abstracting all your database calls so you can easily switch between connection types, but write your system to use on-demand connections, and ensure you code explicitly releases the connection as soon as practical – then see how it behaves.

C.