Web Hosting Talk







View Full Version : bandwidth slow until apache restart


Blueheaven
11-12-2004, 01:51 AM
Ive noticed that all webpages seem to be slow until, i restart apache
Obviously I cant restart the service everytime I want to get good speed, so how can i fix this problem

I've had a look at my message/logs
and that keeps coming up with eth=0 tcp=drop

I've installed zend with mmcache configured with zend
My server load is only .26

Memory usage is at around %50
and swap file is at around 90%

The server is only getting about 50k impressions a day combined
and data transfer has dropped to about 20 gig a day combined
There are however over 50 ftp clients, could this be clogging up the server?

Any solutions would be greatly appreciated

kloch
11-12-2004, 02:59 AM
Originally posted by Blueheaven
Ive noticed that all webpages seem to be slow until, i restart apache
Obviously I cant restart the service everytime I want to get good speed, so how can i fix this problem

I've had a look at my message/logs
and that keeps coming up with eth=0 tcp=drop

I've installed zend with mmcache configured with zend
My server load is only .26

Memory usage is at around %50
and swap file is at around 90%

The server is only getting about 50k impressions a day combined
and data transfer has dropped to about 20 gig a day combined
There are however over 50 ftp clients, could this be clogging up the server?

Any solutions would be greatly appreciated

Are you serving large files with apache?
What kind of disks are you using?

linux-tech
11-12-2004, 04:05 AM
Check the size of your logs (if cpanel, /usr/local/apache/domlogs and /usr/local/apache/logs).
As well, make sure maxclients can handle what you're throwing at it. Most don't change it, leaving it at 150, and 150 is great if you've only got a few sites, but it should be raised if you have more than say 20 popular sites.

Both of these can lead to slow response times in apache, particularly the first. If the domlogs or logs are larger than 1g, clear them out, restart apache, and make sure you clean them out nightly when CP runs it's stats.

firestarter
11-12-2004, 04:25 AM
You can set a cronjob that will delete the domogs that are more than the 1GB.

Blueheaven
11-12-2004, 04:39 AM
Ok ive deleted a few big log files, i had max connections set at 300 and bumped it up to 400.

but I think what made a big difference was setting my timeout lower, it was originally set at 300 and Ive changed it to 60 seconds

assuredhost.com
11-12-2004, 03:45 PM
If it is a cPanel/WHM server - run /scripts/apachelimits and then install SIM.