On Thu, May 2, 2013 at 1:34 PM, Michał Nowotka <mmm...@gmail.com> wrote: > http://www.techempower.com/benchmarks/#section=data-r4 django performance is > really bad comparing to other popular web frameworks. Are there any plans to > change this situation?
First, there are some very serious problems with those "benchmarks" -- they aren't really comparing apples to apples at all. There's some interesting things to dig into with that work, but stating categorically that this "proves" that Django is "slow" is... a stretch. Second, raw speed isn't everything. Scalability, ease of use, suitability, and many other factors play into the decisions we make about technology. If we only cared about raw speed, we'd all still be writing assembly. Finally, of course we care about performance, and we're constantly monitoring and improving Django's speed (see https://github.com/jacobian/djangobench, for example). If you'd like to help, there's plenty of low-hanging fruit, feel free to dive in. But let's not pay *too* much attention to a badly-designed study with unclear goals and intentions. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
