There's all the user crontabs of course, also check for filenames under /etc/cron.hourly, these will as the name implies get run hourly. This doesn't rule out some script somewhere that does this of its own volition either, just a "while true ; do sleep 3600 ; hog_system ; done"
Depending on your system your version of ps may be able to print a tree of what created what process (or at least what process belongs to what process), potentially helpful for tracking down what's spawning the monster. Try ps -ejH
I wouldn't expect a high load average to lag the system, Linux is pretty good at keeping responsive despite high CPU load, but if something's hogging disk access -- like many instances of md5sum could -- that'd definitely slow things down by turfing useful things out of cache.
I recently signed up for a VPS with CentOS and CPanel/WHM. The exact same thing is happening on mine. Spikes every hour, on the hour. They last about 4 minutes and during that time there is piss poor system performance.
High IO Wait time. Memory levels are fine. No RAM swapping.
I monitored top during these spikes and the process that kept floating to the top was: md5sum
---------- Post updated at 03:42 AM ---------- Previous update was at 03:37 AM ----------
By the way, how do we fix what is going on? I am running "ps -ejH" but not sure what to look for. It is neat looking at the process tree! Sweet command.
There is a bit more going on that what these snapshots are showing you. If you saw my top during that time, I had a constant iowait around 50-80% despite lfd/md5sum showing significantly less CPU utilization.
I think the root issue is the way the CSF firewall was configured out of the box. Every 3600 seconds (60 minutes), it's doing a "System Integrity Check". Here is what they have to say about it:
I am going to set it to 0 to see if this solves the immediate problem.
---------- Post updated at 06:04 AM ---------- Previous update was at 05:28 AM ----------
bingo! the iowait for this hour is back to normal levels! I'll keep an eye on it today.
Low CPU doesn't mean it's not thrashing the disk. In fact low CPU on something with no built-in delays like md5sum probably means it IS thrashing the disk.