While checking up on some cronjobs at YouTellMe we had some problems with large cronjobs that took way too much memory. Since Django normally loads all objects into it's memory when iterating over a queryset (even with .iterator, although in that case it's not Django holding it in it's memory, but your database client) I needed a solution that chunks the querysets so they're only keeping a small subset in memory.
Example on how to use it:
my_queryset = queryset_iterator(MyItem.objects.all())
for item in my_queryset:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
import gc def queryset_iterator(queryset, chunksize=1000): ''''' Iterate over a Django Queryset ordered by the primary key This method loads a maximum of chunksize (default: 1000) rows in it's memory at the same time while django normally would load all rows in it's memory. Using the iterator() method only causes it to not preload all the classes. Note that the implementation of the iterator does not support ordered query sets. ''' pk = 0 last_pk = queryset.order_by('-pk').pk queryset = queryset.order_by('pk') while pk < last_pk: for row in queryset.filter(pk__gt=pk)[:chunksize]: pk = row.pk yield row gc.collect()
More like this
- Image compression before saving the new model / work with JPG, PNG by Schleidens 4 days, 14 hours ago
- Help text hyperlinks by sa2812 1 month ago
- Stuff by NixonDash 3 months, 1 week ago
- Add custom fields to the built-in Group model by jmoppel 5 months, 1 week ago
- Month / Year SelectDateWidget based on django SelectDateWidget by pierreben 8 months, 3 weeks ago
Django does not load all rows in memory, but it caches the result while iterating over the result. At the end you have everything in memory (if you don't use .iterator()). For most cases this is no problem.
I had memory problems when looping over huge querysets. I solved them with this:
Check connection.queries is empty. settings.DEBUG==True will store all queries there. (Or replace the list with a dummy object, which does not store anything):
Use queryset.iterator() to disable the internal cache.
Use values_list() if you know you need only some values.
Thanks. It saved my day!
The only issue I encountered is that the function throws an exception when the queryset is empty (no result).
Thanks, this worked great for a table I have with 250,000 rows in it!
In terms of handling an empty queryset the following should work:
What would happen if the entry with last-pk gets deleted during this process? Then I guess pk would never reach last-pk, and the loop is infinite?
Please login first before commenting.