Re: django 1.4 memory issues

You could create a bug report:

https://code.djangoproject.com/newticket

On Tuesday, June 12, 2012 4:59:08 PM UTC+2, Greg Donald wrote:

Over the weekend I upgraded my project to Django 1.4.  After the
upgrade my Apache/mod_wsgi setup began running out of memory.  I
increased the memory capacity of my virtual servers, but that only
extended the time until they began to swap again.  I found a blog
article that suggested setting Apache's MaxRequestsPerChild to
something other than 0.  After setting it to 25, Apache seems to be
releasing memory again.

My question is, why did I have to do that?  The only thing that
changed is my Django version from 1.3 -> 1.4.  I have Debug=False in
settings.py, so I don't think I'm experiencing the SQL memory buildup
described on a couple of blogs.  I do have some long running scripts
that use Django outside of Apache, so I implemented db.reset_queries()
in those, but it had no noticeable effect.  They didn't appear to be
using any more memory than normal, but I figured it couldn't hurt.

So everything is running fine again, but something changed in Django
1.4 that causes my same project code to leak memory.  I'd sure like to
figure it out.

Thanks.


--
Greg Donald

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/QvpMw9Ra7AcJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.