Epilogue: it looks like the major culprit behind my skyrocketing memory usage was indeed my failure to properly restart all the apache processes; it looks like the parent process was still storing debug info from when I had DEBUG=True in my settings.py, so that setting it to False and soft restarting via apachectl had no effect. For the past couple of days memory has been sitting between 30-35MB, which is a hell of a lot better.
While I was looking up memory optimization stuff I stumbled upon a couple of useful links I'll throw out for posterity's sake: http://www.car-chase.net/2007/apr/30/django-deployment-lessons-learned/ http://emergent.urbanpug.com/?p=60 http://blog.webfaction.com/tips-to-keep-your-django-mod-python-memory-usage-down A couple of people pointed the Webfaction crew to Graham's comments and they say they're looking into the mod_python setup, so hopefully that leads to some results down the road. They've also been testing Litespeed/FastCGI setups, which might help with limiting memory usage via FastCGI config. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
