@macdonjo

We’d definitely need to see the logs in this case – for Apache, MySQL, and Django; unless you know which service is going down, in which case we should take a look there first.

Traffic wise, 500-1,000 visitors a day shouldn’t cause that much stress on a 2GB Droplet, so my initial thought would be that you need to fine-tune Apache + MySQL.

What I would recommend starting with is Apache unless your application doesn’t rely on caching of MySQL queries and fetching cached data (for repeated requests for the same thing, in cases where data doesn’t change instantly from requests to request). In this case, you may need to do both.

To start with Apache, backup your current configuration, then try something such as:

KeepAlive On
KeepAliveTimeout 10
MaxKeepAliveRequests 100
MinSpareServers 5
MaxSpareServers 10
StartServers 5
MaxClients 150
MaxRequestsPerChild 300

In your configuration, you have both MaxRequestWorkers and MaxClients – looking at the Apache documentation, MaxRequestWorkers is what it’s called now, so you’re essentially setting the same thing twice. So you can remove the MaxClients setting altogether.

’MaxRequestWorkers was called MaxClients before version 2.3.13. The old name is still supported.’

https://httpd.apache.org/docs/2.4/mod/mpm_common.html#maxrequestworkers