It's a different aproach. I consider my cache attempt a optimization like URL dispatcher cache, without considering django cache system, like url resolvers cache, _join_cache in orm or other many cases. Also, I'm not sure that #6262 consider the inheritance problem (look at copy.deepcopy(self.get_parent()) line in my patch).
On 25 sep, 00:30, Johannes Dollinger <[EMAIL PROTECTED]> wrote: > Am 25.09.2008 um 00:10 schrieb Manuel Saelices: > > > > > > > Hi, > > > one week ago I've made a little change in template rendering engine to > > get a huge performance improvement, in template rendering: > > >http://code.djangoproject.com/ticket/9154 > > > The optimizations where two: > > 1) cache loaded templates that becames compiled. In a threaded > > environment, with many concurrent requests, this can be a huge boost. > > > 2) be able to cache inherited templates. A template with {% extends > > %} tag will compile parent template all times. This of course is not > > necessary. > > > I've test this patch in my projects and only with this I've gain 100% > > of requests per second (with "ab -c 10"). This is fantastic because > > only a little percentage of request is waste on template rendering. > > > I'm so stranged because nobody has comment this ticket. I don't know > > if other people don't find useful or is only that nobody look at this. > > I think this kind of improvement would fantastic for community and for > > comparing other frameworks and templates engine. > > Have you seenhttp://code.djangoproject.com/ticket/6262? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
