On Sat, Nov 2, 2013 at 4:50 PM, Daniele Procida <[email protected]> wrote: > > But, the real killer is the combination of ordering (in the queryset or on > the model, it doesn't matter) with the distinct() - as soon as one is removed > from the equation, the execution time drops to around 250ms. > > That's for 55000 BibliographicRecords created by that last operation (before > distinct() is applied; distinct() reduces them to 28000).
Do you happen to use PostgreSQL? This could be a case of a "non-optimal" configuration, that makes PostgreSQL use the disk to do the sorting. Take a look at http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-WORK-MEM. Apostolis -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAEa3b%2BoCFp3oPwtcR-uyoERW3YwHR4aXLubp7WUpa%2BHtYNhvmw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
