On Fri, Jul 8, 2011 at 8:03 PM, akaariai <akaar...@gmail.com> wrote:
>
> Trying jinja2 in your project is hard - you are using some template
> tags, and you would need to port them to jinja2. Then you would need
> to rewrite your templates so that they work under jinja2. This would
> take some time for sure.
>
> What you could do is check out the profiler suggested in this thread.
> Jinja2 is generally somewhere from 5x to 10x faster that Django
> templates. So if you can see that half of your time is spent in
> template rendering, then you could probably almost double the speed of
> your application using Jinja2. If you don't want to do that, you can
> check how fast your code is without any template rendering: just
> return HttpResponse("") from your view. But remember to evaluate your
> queries, querysets are evaluated only on access. This will give you
> some clue how much Jinja2 would benefit you.
>
All the benchmarking that i have seen till now has clearly placed Jinja2
perform
way better than django templates and this has made me think; as i like
taking
the juice our of every piece of code.
Having said that, i want to brainstorm on how the djano ecosystem can be
made in
such a way that the apps that are written are template-engine agnostic.
For eg, i use many 3rd party apps like endless-pagination, ajax-selects,
uni-form etc which are mainly 'template-specific' apps. (And i *love* all
these apps to the core!)
# How easy/tough is it to move a site which already uses django templates
over to jinja2?
# What are the points that one should be aware of?
-V <http://about.me/venkasub>
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
