Bren, I hear ya, but I'm finding a lot of easy fixes while I really pick through my (not-very-good) code. It's been pretty instructional.
Thanks to everyone for your suggestions. Lots to chew on here. On Mar 7, 3:50 pm, "Bren" <[EMAIL PROTECTED]> wrote: > Personally, I would not get into those details until you profile your > database. Like someone else said, if you're using MySQL turn on the > slow query log. If you run Postgres I'm sure you can find plenty of > documentation about how to monitor and tune that. I just did this and > found two queries that were taking over a minute each to complete, so > this was very helpful. > > Also, do you do any caching? > > I would start with the big stuff and see if that helps with > performance. > > On Mar 7, 3:18 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > On a more specific note, I'm finding lots of places I've done > > something like: > > if request.user.is_authenticated() and request.user.is_staff): > > > It seems to me there's a redundant check being made there. Wouldn't > > one have to be authenticated for is_staff to evaluate to true, meaning > > I can safely just say > > > if request.user.is_staff? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
