I would go with waitress at this point unless you have to support non-WSGI applications. It is very efficient and stable and doesn't require you to run it behind a proxy server (varnish/nginx) if you don't want to.
The only way to get comparable performance from another Python webserver would be to use something like gunicorn or uwsgi with a corouting worker like gevent or eventlet but then you have to make sure you are 100% compatible with those workers which is a pain and can cause a lot of misery if you find 1 part of your stack isn't "greened". The battle tested threaded worker model works so well and along with their asyncore buffering it allows all the benefits of using a proxy server and all the benefits of a wsgi server in one tiny little package! - John On Sun, Mar 9, 2014 at 4:46 AM, Chris Withers <[email protected]>wrote: > Hi All, > > What are the things you should consider when deciding between waitress and > mod_wsgi when it comes to serving a pyramid app? > > cheers, > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" 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/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
