Thanks for the help guys. I started trying to log things, and only then did I notice that I'd missed the obvious - one of the few queries was taking 11s!
Turns out it was a pointless join from a weird use of queries (a queryset contructed one place with more filters added elsewhere in an odd order). Also turns out that, as expected, it was a case of having a much smaller set of test data on my dev server, so it wasn't all that slow on there. Fixed (I hope - its now loading in at most 2s, disappointingly it still doesn't seem to make much odds whether it hits the cache or not...) by just making the query a bit more sane. I suspect there's a few more places where I can improve on similar things that just aren't causing such a headache because the data set isn't so big for a different model. Thanks, Pete -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
