Is there any plan to improve the performance of "render"?
I use django-debug-toolbar to analyze my website and noticed a lot of time is consumed by template render. In my each page, I have about 10ms in database queries, and about 100 ms in render. Thanks. --Fuhong -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/aOh9RzHhxqUJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Is there any plan to improve the performance of "render"?
Le 12 sept. 2012 à 18:56, 富弘刘 a écrit : > I use django-debug-toolbar to analyze my website and noticed a lot of time is > consumed by template render. In my each page, I have about 10ms in database > queries, and about 100 ms in render. Hi Fuhong, Yes, the Django Template Language is known to be rather slow. Compiling it is a very hard problem, for two reasons: - its scoping semantics don't match Python's (unlike Jinja2, for example); - custom template tags can dynamically implement arbitrary behavior. The outcome of the latest attempt is documented here: https://github.com/mitsuhiko/templatetk/blob/master/POST_MORTEM I'm not aware of more recent work on this topic. Best regards, -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Is there any plan to improve the performance of "render"?
On Wed, Sep 12, 2012 at 12:56 PM, 富弘刘 wrote: > I use django-debug-toolbar to analyze my website and noticed a lot of time > is consumed by template render. In my each page, I have about 10ms in > database queries, and about 100 ms in render. Have you tried using the cached template loader (see https://docs.djangoproject.com/en/1.4/ref/templates/api/#loader-types)? Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
#16774 Backtracking URL resolver
Hi, I looked at https://code.djangoproject.com/ticket/16774 and decided to implement the feature where views can raise urlresolvers.DoesNotResolve to make URL Resolver to keep searching for a URL. The diff is here: https://github.com/meric/django/compare/ticket_16774 It introduces a new Exception class and adds a loop to the BaseHandler.get_response. Can a committer or developer look at it? It's quite different to the previous patch looked upon favourably by a core developer 10 months ago. Thanks, Eric -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/zssVpldzQCIJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.