If anything, I’d decrease the log file size as the bigger the file gets the more ‘turn around’ room it will need. The increase of the buffer pool size sounds right to me.
I don’t know anything about ‘droplets’ but the name screams ‘tiny’ to me. You might need to separate out your database to its own server at some time soon. Maybe a second droplet to start? Ask your host for recommendations.
Sometimes an active and growing site needs more hosting than what the cheaper plans can provide though they may be fine to get started from. Nothing says you must have your database and site on the same server.
@jnashhawkins Alright. I’ve decreased the log file size to one fourth now. I.e. 16Mb
I don’t know anything about ‘droplets’ but the name screams ‘tiny’ to me. You might need to separate out your database to its own server at some time soon. Maybe a second droplet to start? Ask your host for recommendations.
So this same site has handled 5x the traffic that it is handling now. So I’m just trying to diagnose why now lately all of a sudden the site is going down so much. If it was an issue of running out of memory, that would have been more prominent when the site was getting that much more traffic
@nzt1012 It’s not always traffic either…
Sites get more complex. Log files grow huge before they concatenate if setup to do so.
Plugins often have scheduled tasks. Revisions grow and take up storage space while growing the data structures to deal with those same revisions.
Any tasks that fail due to server horsepower issues requires one or more log entries. Those entries take up space and more horsepower to deal with.
You might offload some of that work with Cloudflare but if your site is stressed response-wise then Cloudflare might make that worse.
I always recommend ‘more horsepower’, the quickest way to that with WordPress is to upgrade the server or move the database to a second host.
