Thread

I have a situation where my site is part of a cluster with other sites sharing server resources, including the MySQL server.  The cluster administrator has DB connections per user limited to 40.  At times we’re hitting that threshold and our site errors out.

In order to size the connections we’ll need, its’s important I understand what activities will create a database connection, and how those connections are released.

I understand that query caching plays a role, however I’ve seen conflicting posts here regarding whether query caching impacts the number of connections.  One post in particular says that it does not reduce the number of connections, but that seems contrary to the purpose of query caching.

Would you please give some examples of activities that create a unique database connection, and also expand on that as to how the connections are released?

Thanks!

Hi bobromanko,

As with most content management systems pretty much any pageload is going to involve a database connection even with SQL caching. One thing you could try is switching to Persistent connections via Admin ›  System Preferences ›  Database Settings (note that there are then other considerations).

There are plenty of SQL profiling methods out there, so you could install EE on a local/development server to monitor exactly what’s going on.

Overall though, it sounds like your site may have outgrown the server or hosting package it’s being run on. There’s really no magic bullet in this case.