Graham --
Thanks for the response. I've been cruising around the web trying to
find the best solutions for the maximum open files errors i've been
drawing.
The support team at my host advised me that memcached was the source
of the problem -- but I've been getting different answers from
different people. And I'd love to hear more of what y'all have to say
here.
According to the postgresql server administration manuals, there is a
setting called `max_files_per_process` that could be tuned as well. My
main memcached concern is that I'm only getting a 20 percent hitrate,
according to django-memcached reports. And that's despite the fact
that I've configured the machine to do a Django-ish sitewide cache. A
sysadmin I consulted suggested that my memcached startup command might
have an error.
I ran:
$ memcached -d -p 11211 -u nobody -m 64 -c 1024 -P /var/run/memcached/
memcached.pid
And he suggests:
$ memcached -d -p 11211 -u nobody -m 64 -c 1024 -P /var/run/memcached/
memcached.pid -l
127.0.0.1:11211
To answer your question, my global apache conf has these basic
settings:
$ httpd -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c
And from httpd.conf...
Timeout 20
KeepAlive Off
MaxKeepAliveRequests 100
KeepAliveTimeout 5
<IfModule prefork.c>
StartServers 8
MinSpareServers 5
MaxSpareServers 20
ServerLimit 256
MaxClients 256
MaxRequestsPerChild 4000
</IfModule>
Any feedback would be appreciated. I'm a developer who is trying to
take on these sysadmin responsibilities on a limited basis so my
coworkers have space to deploy new development techniques at a low
cost. It's obviously not my area of expertise -- and I'm scandalously
dependent on the kindness of strangers (and bloggers!) like
yourselves.
Thanks again for your great product and support community.
On Apr 20, 5:38 pm, Graham Dumpleton <
Graham.Dumple...@gmail.com>
wrote: