Are you running with the same data set both places? The biggest speed problem I ever had in deployment was because real data blew the database up with a huge join. My dummy data on the test box didn't evoke it. (Fix was to get a simple query set and loop over it so that another query could be qualified without a m2m join).
Bill On Tue, Sep 28, 2010 at 12:12 PM, Shawn Milochik <sh...@milochik.com> wrote: > Do you see anything at all like this if you run your app from your > development box? > You can always use the Python debugger to trace for your code and look for > bottlenecks. > (Awesome tutorial) http://www.doughellmann.com/PyMOTW/pdb/index.html > Also, put in logging and add log.debug statements in various stages of the > code. From the timestamps you can home in on the trouble spot. > Shawn > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@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. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
