By mike3k on

I'm getting warnings from my hosting company that my Drupal-based site macmegasite.com is using too much CPU time.

The last time this happened I already archived my older articles to static pages. I removed a few blocks such as popular content, calendar to browse archive, etc. which I figure would use a lot of CPU time when rendering the page.

Does anyone have any more ideas for reducing Drupal's CPU usage?

Comments

aries’s picture

aries commented

A quick ask: did you enabled the cacheing?

The throttle module can be the answer. It's in the Drupal's core, you can specify components to suspend their functions while you have a huge load. Sometimes to turn off the search function can solve the problem, in that case, if there are DOS-attack. Otherwise it won't.

Can you provide some statistics?
--
Fehér János aka Aries
http://aries.mindworks.hu

mike3k’s picture

mike3k commented

Here are my current stats:

Successful requests: 44,585
Average successful requests per day: 45,275
Successful requests for pages: 8,536
Average successful requests for pages per day: 8,667
Failed requests: 12
Redirected requests: 22,462
Distinct files requested: 16,349
Distinct hosts served: 4,239
Data transferred: 632.89 megabytes
Average data transferred per day: 642.71 megabytes

Yesterday I got a warning from Dreamhost that my CPU minute usage for was 102.02.

Almost 50% of my hits are the RSS feed, so I'm already using FeedBurner with a redirect for /node/feed in my .htaccess.

I do have caching enabled, but I see a lot of errors for duplicate cache entries in my log. I just eliminated a lot of blocks from the front page and reduced the number of articles shown.

--
Mike Cohen, http://www.mcdevzone.com/

he_who_shall_not_be_named’s picture

he_who_shall_not_be_named commented

Protect your cro.php first. I could run http://www.macmegasite.com/cron.php which isn't good.
Also, on the page 4 I have got the "Failed to parse RSS feed MacUpdate: not well-formed (invalid token) at line 101.
Failed to parse RSS feed MacUpdate: not well-formed (invalid token) at line 101." errors. May be you must reduce your feeds update frequency and review your aggregator settings.

-------
http://www.para.ro/en

mike3k’s picture

mike3k commented

Yup, last night I reduced the aggregator update frequency to 3, 6, and 12 hours and eliminated one feed.

--
Mike Cohen, http://www.mcdevzone.com/

doc2@drupalfr.org’s picture

doc2@drupalfr.org commented

Please tell use, how to protect this file?
It's not said in the install files...