Hi all, I didn't follow this PR as it was in progress, but I just sat down and read them. I have to say I'm extremely saddened by https://docs.djangoproject.com/en/dev/topics/performance/#alternative-software-implementations. This seems like extremely bad advice to me.
In my work I've had the opportunity to do performance work across a huge number of applications, and there is an amazing corrolation between people who insist their application is strictly IO bound, and applications which I find 30% wins in just by switching to PyPy. PyPy is known to provide substantial performance gains on Django's template engine ( http://speed.pypy.org/comparison/?exe=1%2BL%2Bdefault%2C2%2B472&ben=3&env=1&hor=true&bas=none&chart=normal+bars), at the time of writing it's something like 10x. Further, the claim that "Any gains are likely to be small, and compatibility issues are common." is pure FUD, and unsubstantiated. I'd strongly prefer we remove this from our docs, and if anything we should be encouraging the opposite, people with performance issues should be encouraged to consider things like PyPy, not hide from them. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084 -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
