On Fri, 5 Jun 2020 13:58:47 +0200 Johan Schiff <jo...@radkompaniet.se> wrote:
> I still think the wrong call was made here [...] > *(Assuming queryset should be evaluated is probably correct in > most cases, but sometimes adds a big performance hit when the code > goes into production and the dataset grows - code that looks > reasonable and works like a charm in dev will cause trouble in > production. Assuming the opposite would have added a tiny performance > hit in most cases, but avoided the big one.)* > FWIW, when that call was made, the default behavior was to fetch only 100 records at a time, so the performance hit for the cases you describe was quite limited. This was changed later, as Tim mentioned in this thread: > Django 1.6 when chunked reads were removed from QuerySet iteration: > > https://github.com/django/django/commit/70679243d1786e03557c28929f9762a119e3ac14 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20200605224258.783815ec.shai%40platonix.com.
