Hi all, I have a deployed pylons application using apache and mod_wsgi. After a few days of uptime, some of the apache processes grow to use massive amount of memory (>350mb each). The processes hang onto the memory they used during each request long after the requests have completed. The machine I am running this on only has 1gb memory + 1gb swap, so these processes end up dominating this system's resources. I am looking into refactoring my code to be more memory efficient, but at the same time I would like to know if anyone knows of configuration options that would enable more aggressive garbage collection. The application does not exhibit this behavior when running with paste, so im not sure how to proceed. I deployed with mod_wsgi to reduce complexities since this application is being served over https and uses our universitiy's homegrown authentication system, so it seemed easier to me to deploy this way. Right now, I have a cron job set up to restart apache to clear its memory usage every night when the application is not in use, but this is obviously a kludge. If anyone has suggestions (configuration ideas, ways to profile, etc), I would be thankful.
-Charlie -- Charlie Meyer [email protected] http://www.charliemeyer.net -- 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.
