I still don't have slow query logging set up, but I am looking at my database, and what jumped out was:
Handler_read_rnd 3,013 k The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly. Handler_read_rnd_next 133 M The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have. Both those numbers seem pretty excessive to me. My question to this board is, what sort of query would lead a newbie like myself into this sort of mess.. in other words, what would be an example of bad code I've probably done and need to remedy? On Mar 7, 4:43 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
