On 1 Dic, 11:55, Graham Dumpleton <[email protected]> wrote: > On 1 December 2010 21:45, Alessandro Pasotti <[email protected]> wrote: >
> > I thought I couldn't use worker MPM because the c/c++ libs used in > > GeoDjango are not thread safe and worker MPS uses threads, but if WSGI > > directives have full control I guess setting threads=1 will suffice. > > You aren't running GeoDjango in the Apache child processes so doesn't > matter that they are multithread with worker MPM as they only proxy > requests. The daemon mode processes that GeoDjango runs in you are > configuring separately and so you can say that for them you have > multiple processes with single thread. > > Graham Thank you for the clarifications, I followed your advice and switched to worker MPM, but the problem became even worse and the server went down with out of memory errors last night. Now I went back to prefork and with this configuration memory seems under control and it's running well: WSGIDaemonProcess ml.eu user=www-data group=www-data processes=10 threads=1 display-name=WSGI inactivity-timeout=240 maximum- requests=100 I also suspect that python 2.5 could be responsible, I cannot switch to 2.6 on that server. I will keep experimenting until I find a stable configuration. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
