Small Spikes in CPU on Wordpress Droplet

Posted on October 16, 2020

Hey guys,

So I have 3 droplets running and two of them are custom websites I’ve built. On those two droplets, my cpu is always around 3 to 5% which is very normal.

However, on my other droplet that is running WordPress on ubuntu my cpu has some small spikes that I don’t know the cause and would like your input on.

I used to have spikes to 100% and I even got the “error establishing data base connection” error on the website sometimes, but now I’ve disabled a plugin that I think was causing that problem and I’ve created a swap memory just in case. That doesn’t happen anymore.

But now I am having small spikes to a max of 20% of cpu for no reason at all, that happens when no one is on the website and I’m not even on the admin panel.

I don’t have any automation going on, is just a basic website with some iframes to some videos on other websites.

Should I be worried about this?

My cpu graph looks like this now :Example

Thanks

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby

October 24, 2020

Hi there @ajcpmoreira,

What I could suggest is to start by checking your access logs to make sure that there is no unusual activity hitting your websites like some bad bots trying to crawl your website or other suspicious activity.

You can find your access logs here:

/var/log/apache/access.logs

You can use the grep command and search for the exact time when the spike happened.

Or you could use the following script to summarize the whole access log:

https://github.com/bobbyiliev/quick_access_logs_summary

Also just in case I could suggest checking your cron jobs to make sure that there are no tasks there which could be causing the spikes, to do so run the following command: