preformance

[JakesSA]

Is it better to keep a persistant connection to a database or to close it after each session?

This would go the same for objects... do you deconstruct them, to do the clean up?

I was wondering about preformance issues! If you get large amounts of traffic to a site, to keep on opening, closing, constructing and deconstructing...I think would cause prefromance issue.

any thoughts?

[jtacon]

Depends ..

If you work with MySQL, keep in mind that MySQL by default only supports 100 connections at same time, if you want to use persistent connections and your site have a lot of traffic, you should increment this number (I think 1024 its the max. value).

If you have the mysql in the same server where there is your http server, I would not use persistent connections. Otherwise, yes, except if the site have too many connections that could cause problems to MySQL.

To destroy the object, I think isn't needed, PHP clears all that from memory after the execution, and usualy, the live of a PHP execution is very short (for web scripting).

[JakesSA]

Thanks

PHP layer is much thinner than that java's, and no where near as memory intensive. I see that version 5 has made room for a deconstructor, so may just good practice to add it in to do clean up.

As for mysql, I think I will close links down, here and there, especially on the bigger queries to free up some recources.

Thanx for the advise, I will keep it in mind.

😃

J