should I be using a mysql_close() anywhere?
PHP will close any non-persistent mysql connections when the script exits. Dont think mysql_close() will solve anything in this case. But if you are going to put it anywhere, put it where you dont need to be connected to the database anymore.
I don't have any sleep() queries anywhere in my code. I don't want them to show up in the process list at all. They just show up and hang the site. I don't know why.
but what is sleeping? it has to be a particular query(s)
That's my struggle, dragon...I need to figure out which query it is, but it seems to happen randomly throughout the site. My main question for this thread is 'should I be closing the connection', but since it is closed automatically when it's not used, that can't be the problem. I do have some ajax httprequests throughout the site, so i'm wondering if that might have something to do with it if a request goes unused? If I figure it out, I'll let you guys know.
it does sound like you actully know if its a mysql sleeping process vs a number of other potential issues.
I added a "kill_sleep" function to my code that is called when the major pages are loaded and the major ajax calls. It will kill sleep processes that are active for 5 seconds or more.
function kill_sleep() {
define ( 'MAX_SLEEP_TIME', 5 );
$result = mysql_query ( "SHOW PROCESSLIST", $this->connection);
while ( $proc = mysql_fetch_assoc ( $result ) ) {
if ($proc ["Command"] == "Sleep" && $proc ["Time"] > MAX_SLEEP_TIME) {
@mysql_query ( "KILL " . $proc ["Id"], $connect );
$display = "KILL " . $proc ["Id"] . "<br />";
}
}
}Everything is working fast and I have not had a sleep() query hanging the site since I put it in. I'll keep testing it. Let me know if you think this is a bad idea.
sounds very dangerous to me, you don't know what process your killing it could have all sorts of consequences.
It turns out the sleep queries were caused by session_start(). I'm using sessions to manage user data throughout the site. Our host is Network Solutions and they put the session data in a temporary directory somewhere. I've also learned that this temp directory may be accessible by anyone on that server.
I moved where my files were being saved by using session_save_path() right before calling session_start();
session_save_path("/data/#/#/#/#/#/user/#/htdocs/#/session");
session_start();(of course, the #'s are filled in with where your values)
I have not had a sleep query and the site runs many times faster. I hope this helps anyone out there who may be having similar problems.
jsnyder2k;10964796 wrote:It turns out the sleep queries were caused by session_start().
odd
jsnyder2k;10964796 wrote:I'm using sessions to manage user data throughout the site. Our host is Network Solutions and they put the session data in a temporary directory somewhere.
thats how they work
jsnyder2k;10964796 wrote:I've also learned that this temp directory may be accessible by anyone on that server.
yup, thats how every shared host does it, but can you guess the session file name? i think they likely hood of some one on a shared host being hacked by another user of the host by grabbing the session data is extremely slim
jsnyder2k;10964796 wrote:I moved where my files were being saved by using session_save_path() right before calling session_start();
session_save_path("/data/#/#/#/#/#/user/#/htdocs/#/session"); session_start();(of course, the #'s are filled in with where your values)
I have not had a sleep query and the site runs many times faster. I hope this helps anyone out there who may be having similar problems.
thanks but odd that helped, unless the host was putting them on a particularly slow drive, the location is more or less irrelevant; and what does it have to do with mysql at all.
Thanks Dragon! It is odd, but the site is amazingly fast right now and users have noticed the difference.
Best,
Jim
dagon wrote:can you guess the session file name? i think they likely hood of some one on a shared host being hacked by another user of the host by grabbing the session data is extremely slim
There's really no guessing needed; [man]glob/man the temp directory for session files and capture them all into your own directory for browsing.
Then again, if you're on shared hosting then you must not really expect much security in the first place, right? 
Can you imagine actully doing that on any shared host in order to maybe hack someone? Can't say i'm worried for any client on a shared host.