http://www.gassavers.org

I just recently noticed that my site is taking an extra second to respond to any click. While it isn't too bad, it's enough to get me worried.

I don't know of a point where it all started happening. I'm assuming it's due to excessive MySQL queries, but i have no idea where to start.

Does anyone have any quick solutions to freeing up resources or making response times faster?

Comments

sepeck’s picture

The quick one is Are you running cron.php on a regular basis? If so, then you will need to start looking at performance of the server in conjunction with your sites usage. CPU, Memory stuff.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Mateo’s picture

I'm running Cron.php every hour so I guess that might do it. I actually had to reboot the server the other day because it quit responding. I noticed load times were much better after that.

sepeck’s picture

Sorry, meant are you running cron.php at all... :) If not some of the maintenence doesn't get done, so running it hourly shouldn't hurt it.

Now we go into more advanced stuff then I do. Hopefully someone who does tuning will stop by the thread.

-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Mateo’s picture

Is it normal for there to be 5 instances of apache running at the same time? Each of them is taking up 26000k of memory.

I can program in php okay, but this linux thing is still new to me.

juerg’s picture

When I run into performance problems, increasing the php memory helped. You can do this either in php.ini or within .htaccess add the line „php_value memory_limit 32M“ or higher.

Regards
Juerg

Mateo’s picture

I'll double check this.

I'm curious to know now if it is normal to have 5 instances of apache and 3 instances of mysql running at the same time. If it isn't normal I'm sure there is a way to prevent it from happening.

andyb’s picture

It's normal to have multiple apache processes running. Each of them is listening for incoming requests. When they receive one they fork a new process, hand off the request to that process, and then start listening for new processes again.

Multiple mysql processes is fine as well - IIRC you get one for each database, plus a "master" process.

Don't worry about the apache memory consumption - a lot of that is shared between the processes. ie, you aren't using 26000 per process, it will be a lot less.