Well crud. My host won't turn on slow query logging. So, if you know you've got a bunch of not-so-good queries (as shown above), how would one try to spot them?
On Mar 10, 4:58 pm, "gilhad" <[EMAIL PROTECTED]> wrote: > On Mar 7, 4:26 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > My site just keeps getting bigger and bigger, and the performance has > > gotten excruciatingly slow. > > ... > > Problem is, I really don't know what to do about it, or even what I > > need to be looking at, really. I've gone through and looked at the > > views and removed imports I didn't need (I had a lot of import * type > > statements), but that only helped a little. I've tried figuring out > > select_all, but don't know if that would really help me or not. > > (-; Very simple test: copy this code to another diretory, attach it to > another nearly empty database and if it hugely speeds up thinks, then > the problem is not in including libraries, but in having big database > and/or bad algorithm for data manipulation. So there lies the way to > get more speed ;-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
