#9154: Huge improvements in templates rendering
--------------------------------------+-------------------------------------
Reporter: msaelices | Owner: msaelices
Status: new | Milestone:
Component: Template system | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Comment (by msaelices):
@mtredinnick, @SmileyChris, This is my honest opinion: I think that
optimizations in #6262 are overdesign. I think using Django cache system
is too hard only for caching compiled templates because:
* It's simpler use a simple global dictionary, like urlresolvers does
(done exactly in [5516]). Common sense said me that a simple solution win
over complex one.
* It's faster that all kinds of cache. memcached can be very fast
compared with a complex SQL in a remote database, locmem can be fast also,
but you will share this with a bunch of cache keys. Database and
filesystem cache can be hundreds of times slower. Also it seems that in
#6262 even with memcached there is no performance improvements.
* Cache system needs templates can be pickable, why you have to add a
requirement not needed at all?
--
Ticket URL: <http://code.djangoproject.com/ticket/9154#comment:14>
Django <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
