Please. As Jacob has already made clear, this thread isn't helping move anything forward. Can we please respect his request and move on.
Django's community is absolutely interested in addressing practical steps towards improving performance and would no doubt welcome specific work towards profiling the request-response cycle or otherwise improving the codebase. The intention may be well-meaning, but links to 3rd party benchmarks without context, comment, or thoughts on actionable tasks are clearly not adding anything to the discussion, and I'm quite sure the core devs have better things to do with their time than thread moderation. - Tom On Tuesday, 16 October 2012 11:36:59 UTC+1, Moonlight wrote: > > another one: > > http://mindref.blogspot.com/2012/10/python-web-reverse-urls-benchmark.html > > > On Thursday, October 4, 2012 10:50:35 AM UTC+3, Moonlight wrote: >> >> I found the following benchmarks recently: >> 1. http://mindref.blogspot.com/2012/09/python-fastest-web-framework.html >> 2. http://mindref.blogspot.com/2012/07/python-fastest-template.html >> >> It is interesting to see the performance boost using pypy. >> > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/x-2TLNJUutgJ. 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.
