Look for somewhere that you're evaluating the queryset. Pagination doesn't need to evaluate it, since it can slice it, which turns into a start and a limit on the database side. Beware of using len() on a queryset (evaluates, IIRC), use qs.count() instead (done on the DB).
On Wed, Oct 17, 2012 at 1:15 PM, Bastian <bastien.roche...@gmail.com> wrote: > I need to paginate a list of images that is getting bigger and bigger and is > loading slowly. I tried the simple django-pagination module but even the > first page takes as long as the whole list to load. I was wondering where to > look but then thought maybe this pagination app only takes the whole list > and then show it page by page. And initially loading the whole list before > paginating it would be as slow as not paginating it. > Should I create a special view that paginates with django.core.paginator and > only returns the results for the current page? Or is it inherent to the very > concept of paginating to load all the objects before doing anything and thus > getting slower as the number of objects get bigger? > Thanks for your help! > Bastian > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/zS6JL9TAdNIJ. > 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. -- 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.
