By mattm on

My website has been closed down due to this reason:

Upon being notified by our monitoring systems or by other clients located on the same server as you, we began to look into resource usage issues caused by your account. Please be aware that resource usage is NOT directly related to bandwidth usage and/or disk space usage. Resource usage is composed of CPU consumption, RAM usage, disk I/O usage, concurrent Apache connections, concurrent MySQL database connections and other system-intensive procedures.

After reviewing your sites and performing an analysis of your resource usage over a period of time, we have determined that the following aspect(s) of your account are the likely cause of the excessive resource usage:

Inefficient index.php page
Average persistant CPU usage: 24.18%

In order to mitigate further Quality of Service (QoS) issues on this server, we have disabled web access on your account. At the moment when users visit your domain they will receive a generic 403 Apache web server error message.

What should I do? Will simply upgrading to the latest drupal fix this? I am running drupal 4.6 right now. Or is it time to look for a more powerful host? Please help, I would like to get my site up as quickly as possible again!

⋅ Categories: Drupal 4.6.x

Comments

varunvnair’s picture

varunvnair commented

Who is your host? Which version of PHP and MySQL? What modules have you enabled in Drupal? What blocks are displayed on the main page? How many members does your site have? How many pageviews does it receive on a day? Is caching enabled?

AFAIK index.php is used for displaying _all_ pages in a Drupal installation. Of course a lot of work is handed off to the appropriate modules, theme engines, themes etc but index.php is called on every page request. So basically your host is pissed off about the resources used by your Drupal installation in general.

Could you ask your host to be a more specific about the resources used?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My Drupal-powered Blog: ThoughtfulChaos

mattm’s picture

mattm commented

My host is site5.com. They run php 4.4.1 and mysql 4.1.14 (http://metis.site5.com/info.php) I have enabled the privatemsg module, image module, forum, buddylist, and the generic comment modules, etc. I have about 10000 pageviews a day, hundreds of members, and the image module carries about 600 images. I haven't enabled caching, perhaps I should try that, since it calculates everything at each page visit I guess.

varunvnair’s picture

varunvnair commented

Enable caching. That will bring down the number of SQL queries for anonymous (not logged in) users significantly. You can flush the cache table (delete from cache;) once in a while so that content remains relatively fresh even for anonymous users.

Disable modules that are of less importance. You can use the devel module to find out which modules are more database intensive and possibly disable them.

Also consider using robots.txt to reduce resource usage by well-behaved bots and the Google Sitemap module.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My Drupal-powered Blog: ThoughtfulChaos

Bèr Kessels’s picture

Bèr Kessels commented

In drupal we call everything trough index.php except the cron.
This means that indeed your site will use index.php for about everything.

However, it sounds like your site has grown too big for the host. You could consider asking them for a bigger account, or move elsewhere.

---
Professional | Personal
| Sympal: Development and Hosting