I am running mod_wsgi in daemon mode with apache worker mpm. Once I start up apache and access my web site, it seems that the apache process then takes up an additional 20m of ram. This memory does not ever get freed up. My virtual host setup is below.
KeepAlive Off <VirtualHost *> ServerName www.findatenant.com ServerAlias *findatenant.com WSGIDaemonProcess findatenant user=bob group=bob processes=1 threads=10 maximum-requests=100 WSGIProcessGroup findatenant WSGIScriptAlias / /home/bob/findatenant.com/findatenantfast.wsgi </VirtualHost> If I try to add the inactivity-timeout argument to the daemonprocess, apache tells me "Invalid option to WSGI daemon process definition" upon startup. I guess I have a few questions here. 1. Why does it not free up the memory? 2. What am I doing wrong that my daemon process line cannot look like this? WSGIDaemonProcess findatenant user=bob group=bob processes=1 threads=10 maximum-requests=100 inactivity-timeout=300 3. If the inactivity-timeout did work for me or it reached the 100 maximum requests and a user is logged in, do they loose their session? 4. I was also messing around with adding additional things to the apache config detailed below. Are these things necessary or even useful with the mod_wsgi options I have set. In an ideal world I would like the processes to free up the memory without messing with people on the site. It would be nice if they went back down right after people were finished with the site. But I would also like it to do a sort of reset once a week. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
