On Fri, Sep 11, 2009 at 10:32 PM, Anand Chitipothu <anandol...@gmail.com>wrote:
> 2009/9/11 Dhananjay Nene <dhananjay.n...@gmail.com>: > > I am curious about the objective .. to the best of my knowledge wsgi is > > essentially blocking (unless my understanding is incorrect), whereas > tornado > > is primarily non-blocking. So would you see any specific advantages of > > deploying a wsgi app with tornado ? > > yes. quite a lot. In a multi-threaded server, as your concurrency > increases thread context-switching overhead will become very high. > Since Tornado uses epoll + callbacks it can handle thousands of > requests. > > The question I was really asking is if an application is modeled as a wsgi application - would it be able to leverage tornado's async / epoll based design. Another post which talks at length about the issue in the context of mod_wsgi + wsgi apps is http://blog.dscpl.com.au/2009/05/blocking-requests-and-nginx-version-of.html > Performance Results for helloworld: > > tornado: 1414 req/sec > tornado + web.py: 802 req/sec > lighttpd + fastcgi + web.py: 354 req/sec > > Tests were run using: ab -n 1000 -c 25 'http://0.0.0.0:8080/' > > Anand > > -- -------------------------------------------------------- blog: http://blog.dhananjaynene.com twitter: http://twitter.com/dnene http://twitter.com/_pythonic
_______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
