http://www.gnorb.net/679/beating-the-life-out-of-my-database Fiction has to be plausible. Reality is under no such constraint. Thu, 26 Jan 2012 04:13:35 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.gnorb.net/679/beating-the-life-out-of-my-database#comment-11166 Nathan Smith Sun, 19 Nov 2006 20:58:19 +0000 http://www.gnorb.net/gnorbnet-updates/20061115/beating-the-life-out-of-my-database/#comment-11166 As your former hosting service provider, I can tell you, that when you were on my server in Edmonton, I wrote a special script - to keep my server from outright collapsing. Remember the "server temporarily unavailable" messages. Basically what the script did, was take down apache and throw up a temporarily unavailable page (complete with the proper error code # so the search engines would understand) until the CPU load went back down to normal. That script kept a log of every time it kicked into effect. Since you left my humble server well, that script hasn't logged one single event. (Apparently your new provider does something similar to prevent one site from collapsing the server). . I think the problem has to do with your flattened URLS. (URL rewrites). Then again I also have a wordpress blog that gets a fair amount of traffic, and it has never blown up the server. . The answer to your problem is a complex one. I can tell you that for sure it's releated to MySQL. What you would need to do, is log MySQL queries or use phpMyAdmin or Mysql's admin tools to tell you what queries are causing the problem (queries that take a long time to execute). Then locate what php script is making that query. To fix the problem - either stop using the php script (if it's a module turn it off), or rewrite the query so it's more efficent, or fix the database structure to make it more efficient. . The other way to troubleshoot is by using the process of elimination method. Turn off one module at a time or disable one script at a time and see if the problem stops happening. . Good luck. Nate As your former hosting service provider, I can tell you, that when you were on my server in Edmonton, I wrote a special script – to keep my server from outright collapsing. Remember the “server temporarily unavailable” messages. Basically what the script did, was take down apache and throw up a temporarily unavailable page (complete with the proper error code # so the search engines would understand) until the CPU load went back down to normal. That script kept a log of every time it kicked into effect. Since you left my humble server well, that script hasn’t logged one single event. (Apparently your new provider does something similar to prevent one site from collapsing the server).
.
I think the problem has to do with your flattened URLS. (URL rewrites). Then again I also have a wordpress blog that gets a fair amount of traffic, and it has never blown up the server.
.
The answer to your problem is a complex one. I can tell you that for sure it’s releated to MySQL. What you would need to do, is log MySQL queries or use phpMyAdmin or Mysql’s admin tools to tell you what queries are causing the problem (queries that take a long time to execute). Then locate what php script is making that query. To fix the problem – either stop using the php script (if it’s a module turn it off), or rewrite the query so it’s more efficent, or fix the database structure to make it more efficient.
.
The other way to troubleshoot is by using the process of elimination method. Turn off one module at a time or disable one script at a time and see if the problem stops happening.
.
Good luck.
Nate

]]>