On Wed, Mar 11, 2009 at 5:31 AM, Malcolm Tredinnick < malc...@pointy-stick.com> wrote:
> > On Wed, 2009-03-11 at 08:13 +0000, Crispin Wellington wrote: > > Hello, > > > > I have a surprisingly simple bit of code, injecting data into a database > > via django's ORM. The "Hit" table has 1.5 million records. The problem > > is, as the loop runs, more and more memory is consumed until my machine > > starts thrashing on swap. the first 400,000 records finishes in 5 > > minutes. Then the next 10,000 take over 30 minutes! As far as I can > > tell, when the 'hit' variable drops out of scope, its ref count should > > go to 0 and it should be garbage collected. It appears it is not, as > > memory usage gradually grows and grows over the loop, bringing the > > machine to its knees. Here is the code snippet: > > It's a reasonable guess, based on you not ruling it out, that you're > experiencing this: > > > http://docs.djangoproject.com/en/dev/faq/models/#why-is-django-leaking-memory > > Regards, > Malcolm > > > > > > Try this method: http://docs.djangoproject.com/en/dev/ref/models/querysets/#iterator Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
