Are you using the cached template loader? It may mitigate the problem to some extent. https://docs.djangoproject.com/en/1.11/ref/templates/api/#django.template.loaders.cached.Loader
As of Django 1.11, it's enabled if DEBUG is False and OPTIONS['loaders'] <https://docs.djangoproject.com/en/1.11/ref/settings/#std:setting-TEMPLATES-OPTIONS> isn’t specified. On Friday, August 4, 2017 at 5:37:59 PM UTC-4, Matthew Pava wrote: > > I finally made the leap to Django 1.11 from 1.10. I thought that I needed > to use the new Subquery, but it turned out that I was able to solve my > problem without using it. Good news for sure! > > > > However, I have noticed that my forms are loading more slowly. > > > > We discovered that when we were using crispy-forms, which we still do, > that there was a bottleneck when including all the widget templates and the > template inheritance involved in rendering the widgets and finally the > final outcome. > > > > And this leads me to conclude that the new widget rendering from templates > built in to Django 1.11 is the bottleneck as well. Does anyone else > experience this issue? Is there a workaround? > -- 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/fa2fe1a4-e5ef-4c58-84f1-325ebcd79891%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
