Cool thanks alot i will look into it too . Try nginx or cherokee as http server then scgi. We using that type of configuration in production with at least 180K json requests a day and very complex business logic with high concurrency. scgi is not much tunable but is really simple: on a machine like yours will do good. I wrote a slice here for a standard preforking scgi setup: http://www.web2pyslices.com/slices/take_slice/143
On Thu, Sep 29, 2011 at 5:13 AM, Phyo Arkar <phyo.arkarl...@gmail.com>wrote: > I really hate apache i will never use it. > > So if i am going to change underlying web engine i want something that > support long polling with concurrency , how about tornado web ? would it be > good > > > On Thu, Sep 29, 2011 at 4:59 AM, Michele Comitini < > michele.comit...@gmail.com> wrote: > >> I wrote: >> > uwsgi uses many different models. Using uwsgi a mix of event + >> > prefork could give a big boost, but if you care about performance >> > avoid apache. >> > >> >> I should have been: >> uwsgi uses many different models. Using uwsgi a mix of event + >> prefork could give a big boost -->and<-- if you care about performance >> avoid apache. I.e. use nginx or cherokee or lighttpd >> > >
