#25228: Performance degradation of template rendering
---------------------------------+--------------------
Reporter: yml | Owner: nobody
Type: Bug | Status: new
Component: Template system | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------
I noticed a performance regression after an upgrade from django `1.6.11`
to `1.8.3` ; the project does an extensive usage of `include` and
`extends`. I have simplified the problem into a mini django project on
github called: [https://github.com/yml/django-perfo-regression django-
perfo-regression]. This project contains 2 branches (different settings)
and 4 tests used to time various cases of template rendering:
* Standalone
* `include`
* `extends`
* `include` & `extends`
Depending on the settings there has been 2 major changes in the
performance characteristic over the releases since django 1.4.
* `1.7` doubled the rendering time with DEBUG=True for `include`
* `1.8.3` degraded the simplified production ready (`DEBUG=False` &
`cached.Loader`)
This [https://docs.google.com/spreadsheets/d/1v-cXcx8lLOF7sphtvdofU-
30GmpPCyvgn1TjIRJk4OM/edit?usp=sharing spreadsheet] contains the result I
am observing on my laptop.
--
Ticket URL: <https://code.djangoproject.com/ticket/25228>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/046.018fe4af1ea5d90c57504c53bb70f5c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
