On Tue, 07 Aug 2012 00:39:36 +0200 Melvyn Sopacua <m.r.sopa...@gmail.com> wrote:
> 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. Thank you very much...it's very helpful. > 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. I've found out about uwsgi's idle & cheap option...very useful. > 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 Thanks a lot. Sincerely, Gour -- Thus the wise living entity's pure consciousness becomes covered by his eternal enemy in the form of lust, which is never satisfied and which burns like fire. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
signature.asc
Description: PGP signature
