On Wed, 24 Feb 2010 19:09:18 +0800 Bernard Chan <[email protected]> wrote:
there is no avoiding that Django apps are memory intensive specially when compared to PHP. Pootle is even worse due to caching parsed translation files to speed translation actions. the larger the file the more memory is used. at the moment the only thing you can do to bring down memory use is by reducing the number of files kept in memory. change the variable PARSE_POOL_SIZE in the localsettings.py file. experiment with very low values first and increase it slowly. you could also try using mod_wsgi's daemon mode to limit the number of apache processes actually running python and let the others just work as a proxy. in theory this should improve memory use at the cost of concurrency. (explained @ http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide) we have not tested daemon mode, so no idea how well it performs. if you do test it please share your experience. cheers, Alaa ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
