Persistent Connections

Posted: Tue May 08, 2007 6:00 pm

Hello guys,

I just got the below note from my new host and wanted to see if anything could be done in Nuke to change this. Has anybody heard this before? Can anything be done?

Quote:

System administration has noted that your account appears to be using persistent connections in some of the software used on your site. Persistent connections are by and large not necessary for most software to function, and they can cause issues with your account.

To explain a bit further, persistent connections are one method PHP scripts may use to open a connection to a MySql database. Using persistent connecting is only useful in an environment with a high overhead in connecting to the MySql database itself - in your case the connection (and 'cost' in resources) is negligible compared to using persistent connections as all of your queries are executed immediately.

The persistent connections in this case are simply sitting idle consuming memory and may bring your site close to the predefined limits set for accounts in the shared hosting environment. If you have a database intensive site, this could make the site appear sluggish or appear to be down while the initial queries time out (this can take up to 300 seconds, depending on several factors).

You will need to review your code and see where these persistent connections are coming from, as spikes in traffic could cause your site to appear to be unavailable to your visitors.

Any ideas or opinions? Running Nuke 7.6.

Sells PC To Pay For Divorce Joined: Posts: 5661

..huh...they can check that..
why dont they ?
in some cases it can help but but it does take up extra resources...
maybe thats what they dont like.

Posted: Tue May 08, 2007 6:57 pm

That's why I wanted to post and find out more. If this is the case, then wouldn't changing a few lines of connection code make Nuke run more efficient?

Posted: Tue May 08, 2007 7:15 pm

Nuke does not use persistent connections. See db/db.php. It is passing in false for the persistent flag to the sql_db constructor. This causes Nuke to call mysql_connect() (non-persistent connect) instead of the persistent mysql_pconnect() call.

Posted: Tue May 08, 2007 7:18 pm

And even for the legacy $dbi variable it is using the non-persistent connect call.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

Many hosts, including Raven Web Hosting, disable the persistent connections so it matters not what the application does.

Posted: Tue May 08, 2007 7:32 pm

Hmmm ok. Thanks everybody. I asked them for a sample query or something where I can determine what in the software is causing it.

Posted: Sun May 13, 2007 10:58 am

I was just looking at NukeTreasury and noticed it was calling mysql_pconnect(). Are you running that module?

I have version 1.0 and this is in the ipnppd.php file that is used for IPN callbacks.

Posted: Sun May 13, 2007 11:27 am

Nope, not running that. The only big things that aren't standard Nuke is the Gallery module and that abandoned Amazon module from PrecioGasolina.com.

Thanks anyway. Smile

Posted: Sun May 13, 2007 12:34 pm

You can always do a find/grep and look for mysql_pconnect(). Smile