I checked the BIOS settings before I ever installed SME8 so I don't think that is the problem. Besides, I think that would be more likely to cause an overall slowdown rather than one that occurs only occasionally.
I'm not sure what I'm looking for on the other tools so I'll report the results. For newrpms I get:
awstats.noarch 7.0-2.el5.rf
[quote author=wdepot link=topic=49932.msg250260#msg250260 date=1369858970]
[code]
powerman.x86_64 2.3.5-2geekery
do not know what it is for and what ressources it use..
smeserver-awstats.noarch 1.2-7.el4.sme
depending on the size of your http logs it can slow your server at every cron
smeserver-diskusage.noarch 0.0.1-13.el4.sme
it can really slow down your server each time you consult the page (du of every folder)
du -sh /var/log/messages* listed about 30 files ranging in size from 8.0K for the one dated today up to a maximum of 5.9M for a file dated on May 11, 2013. I'm afraid I don't really know what I'm looking for there.
huge log (>1 Mo) can slow your server when you are using log parser like sme8admin, awstat, or a lot of system that scan log for security purpose.
Huge log can also indicate a malfunctionning deamon that is sending a lot of crap to your logs in order to tell come to set me correctly. SO I would start to find why your message log is so big !
du -sh /var/log/httpd/* lists something like 30 files named access_log.*, another 30 named admin_access_log.*, 30 named admin_error_log.*, 30 named error_log.* and one file each named awstats_lr and awstats_pos. Again I have no idea what I am looking for.
same here the size of your files would help, if your error logs are > 1 Mo then you have a lot of malfunctioning webapps that should be corrected and might be your problem. Reading these logs could help locating the problem
huge access log would mean alot of traffic, which mean a lot of work each time awstats runs. If this is the case you might want to run it more often.
I've never used htop before but as near as I can tell I basically just displays a constant list of currently running processes with a display of the load on each processor core? I take it that when the slowdown occurs I should see a spike in the number of running processes and processor core usage and should look for processes other than httpd and mysqld?
moreover you should see a process using a lot of resources if you sort by CPU or memory