I think this is just a bad practice in the app logic, or bad logic. you have only 9000records, what other languange out there will be process it faster anyway .
if you have 1Mill records, do you will retreive all that object first and do the processing, and no caching at all . this will make even fastest monster machine seems slow down. optimization of web app is have many path... database loading, caching, compressing content, static file caching serving, keep alive, and many more.. just my 2 cents.. Regards, Mulianto On Tue, Apr 17, 2012 at 1:02 PM, Andy McKay <a...@clearwind.ca> wrote: > Run django debug toolbar, see what queries you are running and how > long they take and that you've got database indexes set up. > > Failing that, run a middleware or other logging tool to tell you slow > pages. Then test with django debug toolbar. Rinse and repeat. > > -- > 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. > > -- 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.
