Hi Gour, On 6-8-2012 18:03, Gour wrote:
> At the moment I (have to) run 3 php sites in a tight memory environment > using lighttpd server & php-fpm and I'd like to move one php site (for > the beginning) to django cms (mezzanine) and wonder what is the impact > of running django app with fastcgi vs wsgi? how they compare > memory-wise? The system used is not of much influence. The bulk of the memory usage of a WSGI and fastcgi app is the modules that are loaded by the python interpreter, similar to how php-fpm memory increases with each extension that is loaded. Caching settings are also of influence. > If wsgi option is better option, what would be optimal wsgi server > memory-wise: uwsgi, gunicorn, fapws..? The best way to find out is to load your apps and turn debugging off on your staging server (settings.DEBUG is a major memory hog). I do however find that uwsgi gives you a lot of control combined with sane defaults. Limits to configure include memory usage and forking models. So you main goal is to turn off in django what you don't need. Candidates: - i18n/l10n - cachemiddleware - context processors - settings.DEBUG - uninstall PIL if you don't use it Hth, -- Melvyn Sopacua -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
