> Use Apache and mod_wsgi and you have all that you want except playing > with 'processor affinity'. This is because Apache is multi process by > design and thus can properly make use of multiple CPUs. A lot of what > goes on in Apache is also not implemented in Python and thus not > subject to GIL issues. > > You might also have a read of the following: > > http://blog.dscpl.com.au/2007/09/parallel-python-discussion-and-modwsgi.html > http://blog.dscpl.com.au/2007/07/web-hosting-landscape-and-modwsgi.html
Read. Apache is starting to look attractive now. So I assume I'm not looking for embedded mode, right? You say it's more performance, but at the cost of what? Using the worker MPM and, say, daemon-mode, using, say, 4 processes and 16 threads each, would my processes be dying as soon as they're not needed? My application takes awhile to load because I autoload my database using SQLAlchemy. Is it that easy to configure apache to start 4 by default and load balance between all of them? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
