[CentralOH] Django Management Command Memory Usage
godber at gmail.com
Mon Jun 4 16:59:12 CEST 2012
I've not had to solve this problem myself, yet. But if I had to
there'd be two things I'd look into. Model pagination and perhaps
using the query cache iterator method.
First comment on:
I'd be interested to know your results if you try either of these.
On Mon, Jun 4, 2012 at 7:28 AM, <jep200404 at columbus.rr.com> wrote:
> How can I reduce the memory usage in a Django management command?
> I have some Django code like follows in a management program:
> class Command(BaseCommand):
> def handle(self, *args, **options):
> for record in Places.objects.all():
> if record.x and record.y:
> record.point = (
> record.point = None
> In the settings.py file I have:
> DEBUG = False
> Places has millions of rows.
> top reveals that the program is using 18.6 Gigabytes of memory.
> How can I reduce that memory usage?
> Am I neglecting to close or release something?
> The only dox I'm finding about memory use related to query sets
> advise to use iterators instead of converting to a list.
> I'm already following that advice, but I'm not finding
> further guidance about memory use about record modification.
> Since DEBUG is False, I've already heeding the following.
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> I have found that the following might be nice,
> but doubt it addresses the memory issue.
> CentralOH mailing list
> CentralOH at python.org
More information about the CentralOH