I recently posted a serverfault question about how to achieve a setup that has the following characteristics:
1. Easy to deploy, really easy. As easy as PHP and PHP-FPM. 2. Seldom used applications would take no resources and oft used applications would be active constantly. 3. Reloading for code changes isn't a giant pain in the ass. http://serverfault.com/questions/281671/uwsgi-virtualhost-mode-with-touch-reload That link contains all of the details and issues that I've run into. To summarize; I was able to mostly achieve all of this using virtualhost mode. However, all of the applications need to be idle for the "idle" option to collect resources. From my tests it appears that if I'm running 10 applications all 10 will remain in memory until they are all idle for the specified seconds, even if only one application is receiving traffic. The other issue was with touch-reload. I could not use touch-reload to reload a specific application on change. In virtualhost mode it would be nice if it were possible to automatically or through specification monitor the specific module that the application loads. Each app has it's own local entry point but the touch reload feature is a global one. Emperor mode was a near alternative but it complicates the webserver config, each app requires its own socket/file and I am worried that loading 10 applications would cause a massive amount of resident processes. Any insights, or suggestions would be appreciated. Trey Long _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
