#22086: Building of template nodelist inside cache blocks
--------------------------------------+------------------------------------
Reporter: HenrikOssipoff | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Template system | Version: 1.6
Severity: Normal | Resolution:
Keywords: template, cache | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
I'm not completely sure I see how the optimisation you describe will help
here -- at some point, the cached node will need to be rendered, which
will mean the node tree will need to be parsed and stored.
However, you've clearly found a performance bottleneck, which deserves to
be investigated.
If you could provide details of the template(s) you're using to manifest
this problem, it would be very helpful for whoever undertakes this task.
--
Ticket URL: <https://code.djangoproject.com/ticket/22086#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.dc66654ecd1824dfe80b67c361a862f6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
