rhyno
04-03-2006, 09:44 AM
Hello everyone.
I am a new member here at Bluehost. Yesterday, I received my first CPU usage ban after installing and playing with G2 on a new domain. According to the log, it looks like its mainly the fullscreen slideshow applet Module of G2(I have since disabled this feature) that was the issue, but there were quite a few queries that spiked the CPU as well.
I understand the reasoning behind limiting the CPU, but I was wondering if another method were possible to ensure the security and reliability of all the customers on box.
Rather than an outright ban, is it possible to throttle the CPU usage of the offending script? In other words, the script would automatically be set to a lower priority process and receive less CPU time therefore making the script take longer to process, but protecting the other customers as well. The owner of the script may receive complaints etc. but there could still be a log entry of the offending script for them to check on.
I'm not sure if this is technically feasible, or what may be needed serverside to make it feasible, but I thought I'd ask. It seems like it would be better than an outright ban (even for 15-30 seconds) for all website visitors to see.
PS. I do appreciate all the explanations of indexing tables in the database. Very informative and something I will be looking into if need be.
I am a new member here at Bluehost. Yesterday, I received my first CPU usage ban after installing and playing with G2 on a new domain. According to the log, it looks like its mainly the fullscreen slideshow applet Module of G2(I have since disabled this feature) that was the issue, but there were quite a few queries that spiked the CPU as well.
I understand the reasoning behind limiting the CPU, but I was wondering if another method were possible to ensure the security and reliability of all the customers on box.
Rather than an outright ban, is it possible to throttle the CPU usage of the offending script? In other words, the script would automatically be set to a lower priority process and receive less CPU time therefore making the script take longer to process, but protecting the other customers as well. The owner of the script may receive complaints etc. but there could still be a log entry of the offending script for them to check on.
I'm not sure if this is technically feasible, or what may be needed serverside to make it feasible, but I thought I'd ask. It seems like it would be better than an outright ban (even for 15-30 seconds) for all website visitors to see.
PS. I do appreciate all the explanations of indexing tables in the database. Very informative and something I will be looking into if need be.