Sorry, forgot to mention. Debug is definitely set to False!
On Nov 22, 2012, at 7:44 AM, Tom Evans wrote:
> On Thu, Nov 22, 2012 at 6:27 AM, Dan Ancona <afightingfa...@gmail.com> wrote:
>> python 2.7.3, django 1.4.2
>>
>> Our app (a fairly simple tastypie API that runs some machine learning foo on
>> mongodb records) is deployed to heroku and is leaking memory at a pretty
>> good clip. Hitting heroku memory errors after about an hour or two, under
>> significant load.
>>
>> Wandered through some various profiling options and eventually started to
>> get suspicious of tastypie. So I tried ripping that out. And then everything
>> else, until I finally got down to a django view that has nothing but this in
>> it:
>>
>> def stack(request):
>> gc.set_debug(gc.DEBUG_LEAK)
>> print "Uncollectable garbage", gc.garbage
>> return HttpResponse('hi')
>>
>> And even that, after a couple reloads, dumps a huge mess, the beginning of
>> which is below. Looks like the whole heap.
>>
>> Any idea what might be going on here or what my next steps are?
>>
>
> Is settings.DEBUG true? Expected behaviour.
>
> Cheers
>
> Tom
>
> --
> 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
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
