Conventional wisdom is that mod_python eats a little more memory than a correctly configured mod_wsgi.
Here are some nice posts about using mod_wsgi in low memory environments: http://groups.google.com/group/modwsgi/browse_thread/thread/d21c334972fc8d37 http://www.technobabble.dk/2008/aug/25/django-mod-wsgi-perfect-match/ Another bit of conventional wisdom is that nginx > lighttpd because of a memory leak in lighttpd, but my favorite endorsement of nginx was Will Larson's. He chose nginx because it was Russian and "therefore exotic": http://lethain.com/entry/2007/jul/17/dreamier-dream-server-nginx/ That, by the way was a blog post that helped me get my production servers up about a year ago using one of the techniques you were asking about called "reverse proxying" where requests for static media are handled up-front by a lightweight server and all other requests are sent through to apache / mod_whatever for the heavy lifting. On Sep 29, 1:37 pm, Kip Parker <[EMAIL PROTECTED]> wrote: > Thanks Frank, that's very interesting. A lack of complaining users is > much to be desired. Have you ever used this set up for multiple sites? > I have about 20 sites running, and there may well be more in the > future. > > It would be excellent also to know what you found painful about > mod_python. > > All the best, > > Kip. > > On Sep 29, 6:23 pm, Frantisek Malina <[EMAIL PROTECTED]> wrote: > > > I wrote a post for you on my > > blog:http://vizualbod.com/articles/nginx-fastcgiwsgi-django-deployment > > > I've tried mod_python and it was a pain. > > > Frankhttp://vizualbod.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
