On Mar 30, 6:18 am, xtrqt <jan.rzepe...@gmail.com> wrote:
> def templ(context, divisibleby=divisibleby):
> my_list = context.get("my_list")
> _loop_len = len(my_list)
> result = []
> for forloop, i in enumerate(my_list):
> forloop = {
> "counter0": forloop,
> "counter": forloop+1,
> "revcounter": _loop_len - i,
> "revcounter0": _loop_len - i - 1,
> "first": i == 0,
> "last": (i == _loop_len - 1),
> }
> if divisibleby(i, 2) == 0:
> result.append(force_unicode(i))
> return "".join(result)
> For comparison here is the performnace of these 2::
> >>> %timeit t.render(Context({"my_list": range(1000)}))
> 10 loops, best of 3: 38.2 ms per loop
> >>> %timeit templ(Context({"my_list": range(1000)}))
> 100 loops, best of 3: 3.63 ms per loop
> That's a 10-fold improvement!
I did a little test by adding localize(i) in there. On my computer the
time went to around 25ms. For datetimes the time needed is somewhere
around 100ms. If you could inline the localize(i) call for the integer
case you would get back to around 4ms, as it doesn't actually do
anything else than return force_unicode(i)... So, when designing
template compilation it is essential to see how the localization stuff
could be made faster, else much of the benefit will be lost. It seems
that at least for this test case localization uses over 50% of the
time, so there would be bigger gain in making localization faster than
in making compiled templates.
- Anssi
--
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.
