On Dec 11, 2007 12:18 PM, Joe <[EMAIL PROTECTED]> wrote: > > I've found the largest memory hog to be the native way related tables > are setup. > > Check class definitions with related tables and edit as such: > > class ...(models.Mode): > relatedtable = models.ForeignKey(RelatedTable, core=True, > raw_id_admin=True) > > The raw_id_admin=True prevents django from pulling up all related > records when the object is loaded etc. While I would have expected > this to only affect the admin side, it had a huge impact on the public > side of our site. Memory consumption went from +500mb to 20-30mb. >
You must be using manipulators in oldforms. Try newforms. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
