On Tue, May 23, 2017 at 6:40 PM, Bernd Wechner <bernd.wech...@gmail.com> wrote:
> James, > > Thanks for the quick look, the tips and more. I am using Django 1.11 and > given your notes a huge suspect because: > > 1. This slow down is very recent > 2. very recently I upgraded to 1.11 specifically because I needed a > subquery on one view > > Rolling back to 1.10 is an option for testing, but I need that subquery. I > will see how much hassle it is to unwind to 1.10 and check the page render > time on that one page. > > Onto your other suggestions, I will follow them through, but further notes: > Another to add to the pile. Try disabling the debug toolbar. I happened to be browsing its documentation for my own project, and I noticed it has a performance tips section. http://django-debug-toolbar.readthedocs.io/en/stable/tips.html#performance-considerations Seeing this, I also glanced through the code repository, and it does reference pprint in a few places when generating the data for display in the panels. If your context is sizable (and based on the template you pointed to, that may be the case), this may explain your delay. Worth a shot. -James -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciWVMMFa6jPJe58bZONKz40SHyGiYVL5S0kYP3dy-mfzpg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.