You can use daemon mode which won't run into quite that much memory growth if you're not running multiple instances. Embedded mode has some different memory requirements.
You might post over on the mod_wsgi list as Graham Dumpleton is very responsive, and knows the ins and outs and probably will be able to tell you the steps to take to debug things. In a recent version he did put in some limit commands. Are you running prefork or worker? You could turn down the max requests per child to cause apache to recycle those processes a little more quickly. If prefork, do you also have mod_php enabled? If you don't need mod_php, mpm-worker/mod_wsgi works quite well. The only thing I can think that would cause that much memory to be used, and the growth over time MIGHT be a memory leak somewhere in the application, or, shared memory that is allocated but not released somewhere. As a last resort you could utilize mod_proxy and cherrypy/paster, but, I think you'll end up with better performance with mod_wsgi/apache2. -- 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.
