Thanks everyone. I might offload some big processes into a separate
process. The background knowledge I've aquired from this thread is
going to help a lot.
I still have no flipping idea how to use heapy though!
On Apr 9, 12:30 am, Malcolm Tredinnick
wrote:
> On Wed, 2009-04-08 at 08:43 +0100, A
On Wed, 2009-04-08 at 08:43 +0100, Andy Baker wrote:
> Wow! So Python will eat RAM until restarted? That changes the way I am
> thinking about this problem.
Well, that's not really accurate, as you realise further down. The
maximum amount of RAM used will not decrease. However, it won't increase
On Apr 8, 5:43 pm, Andy Baker wrote:
> Wow! So Python will eat RAM until restarted? That changes the way I am
> thinking about this problem.
>
> So the trick will be tweaking the number of processes and the number of
> requests allowed between a restart. I know one item requests a big chunk of
Wow! So Python will eat RAM until restarted? That changes the way I am
thinking about this problem.
So the trick will be tweaking the number of processes and the number of
requests allowed between a restart. I know one item requests a big chunk of
memory is dynamic PDF generation.
So lets say thi
On Tue, 2009-04-07 at 15:20 -0700, andybak wrote:
> I've got no really huge tables - the entire db is under 6meg and the
> site isn't even public yet so traffic is minimal. Memory just doesn't
> seem to go down. (until the process get's restarted by maxchild or by
> me killing it).
That's complet
I've got no really huge tables - the entire db is under 6meg and the
site isn't even public yet so traffic is minimal. Memory just doesn't
seem to go down. (until the process get's restarted by maxchild or by
me killing it).
I have been labouring under the assumption that memory gets freed
eventu
Alex Gaynor wrote:
>> I recently had a proces hog about 1.8 GB RAM when looping through a
>> queryset with approx. 350k items as:
>>
>> for obj in Model.objects.all():
>> do_something(obj)
>>
>> I rewrote it to:
>>
>> objs = Model.objects.all().values_list("id", flat=True)
>> for obj_id in obj
On Tue, Apr 7, 2009 at 6:02 PM, Christian Joergensen wrote:
>
> AndyB wrote:
> > I've got a Django app that seems to eat up a lot of memory. I posted a
> > message on Stack Overflow and it got a little sidetracked into a
> > debate about the merits of WSGI and Apache in Worker MPM mode.
>
> First
AndyB wrote:
> I've got a Django app that seems to eat up a lot of memory. I posted a
> message on Stack Overflow and it got a little sidetracked into a
> debate about the merits of WSGI and Apache in Worker MPM mode.
First thing - make sure DEBUG is set to off.
If that's not the problem, Let me
I've got a Django app that seems to eat up a lot of memory. I posted a
message on Stack Overflow and it got a little sidetracked into a
debate about the merits of WSGI and Apache in Worker MPM mode.
Webfaction have assured me that playing around withthat kind of thing
is not going to make a signi
10 matches
Mail list logo
