Il giorno 08/mar/2011, alle ore 12.09, Simon Litchfield ha scritto: > > On 08/03/2011, at 7:48 PM, Roberto De Ioris wrote: > >> Ok, so we need to understand what is blocking your workers. > > It turns out memcache connections were not being closed. > > I've stopped using python-memcache 1.44, and switched to pylibmc. So far so > good. > > Previous modwsgi server was running python-memcache 1.45 and memcached 1.4.5 > (current is 1.4.2).
mod_wsgi (or better, apache in this case) recycle processes so connection get closed at every respawn. You can emulate this with --max-requests, but i found it useful only for avoiding memory leaks. If your app is good you do not need it. > >> Just for being scrupulous add >> >> --close-on-exec > > What does it do? avoid children processes to inherit the uWSGI connection socket. It is probably useless for you :) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
