On Wed, Jan 20, 2010 at 10:58 AM, Phil Christensen <p...@bubblehouse.org> wrote: > On Jan 20, 2010, at 1:19 PM, adamjamesdrew same wrote: >> Is twisted WSGI production ready as compared to apache and mod_wsgi >> >> For a simple server with 4 cores would you simple start 4 instances and load >> balance between them? >> How would you recommend a production deploy of twisted wsgi? > > Twisted's WSGI support is definitely production-ready; I'm currently using it > in several production environments at work. > > However, performance can be limited by its use of Python threads, and the > impact of the Global Interpreter Lock (which would be somewhat negated by > your plan of running 4 instances in a load-balancing pool). > > If you need extremely high performance (and I mean really need -- Twisted > WSGI is fast enough for many many scenarios), you will probably want to use > another WSGI container. Yes, twisted performs great for normal loads. And, if you are so lucky to suddenly have a massive amount of users and you need to scale up, I'd suggest trying out the Nginx wsgi support, which I use in a couple apps and works great.
-Alex > > But of course, that's the benefit of coding to the WSGI spec. Personally, I > use Twisted's WSGI for development, and for medium-load production > deployments where I need a web server directly integrated with other Twisted > code. > > For production, I've had great success with mod_wsgi on Apache 2.2, which I > believe is the standard deployment environment for Django, as well. > > -phil > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > -- Alex Clemesha clemesha.org _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
