On Thu, Jan 29, 2009 at 7:41 AM, Tipan <t...@ortengo.co.uk> wrote: > > Can anyone suggest some areas to explore to improve the response time > on the Admin. We're currently on release 7476 (pre new forms admin), > but due to go to the latest development release next week, although > I'm not sure how significant this will be as we've always had a > reasonably responsive admin side, only slowing as the user traffic has > grown, but I still don't think this level of traffic should be > bothering our set-up.
Without specifics, it's a little difficult to say for certain, but one of the reasons for the switch to newforms and newforms-admin was to eliminate some very expensive querying behavior in the manipulators behind forms. This wasn't a matter of one big query that was expensive - but you could easily end up with a very large number of very small queries. As your user base expands, it's entirely possible that the flood of little queries is adding up and slowing down the site. The other obvious place to look is where Karen noted - Foreign keys with very large selection sets. The raw id field option is one way to address this; another approach is to write a custom widget that doesn't try to load the entire selection set. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
