mysql_close

Posted: Tue Feb 06, 2007 10:56 am

When I complain of speed, my host thinks I need more information on closing db connections.

I've googled and read otherwise. And, I just did a search of my latest RN and didn't find any instance of mysql_close.

If I didn't find it in RN, is it required in my stand alone scripts?

I'm confuddled, again.
I know there is a mysql config in php.ini that might improve performace, but I don't know what I'm doing because I don't understand what it is I should be doing.
And, of course, the hosts suggested a fix might only require buying more memory.

Opinions and clues? Logs I should be scanning?

Have a happy nuking day.

Sells PC To Pay For Divorce Joined: Posts: 5661

mysql_close() closes the non-persistent connection to the MySQL server that's associated with the specified link identifier.
Using mysql_close() isn't usually necessary, as non-persistent open links are automatically closed at the end of the script's execution.

so what the question realy is in this isnt that clear...
naturaly no host is gonna confess that speed is bad or whatever...
btw...a standard configuration is sufficiant enough...

Quote:

fix might only require buying more memory

nice story...

registered · Posted: Tue Feb 06, 2007 4:39 pm

speed: cause by non-optimized queries.

To test it, echo or log all database queries (echoing is better, that way you see how much queries get executed)

Then place the word EXPLAIN in front of each SELECT query and run them one at the time in your favorite sql manager.

You will notice the massive amount of indexes missing.

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

mysql_close is almost always NOT needed. It actually slows down your scripts. So, your host need to be educated Smile