+1: I really don't see the issue with uwsgi configs .

Il giorno mercoledì 2 ottobre 2013 15:16:23 UTC+2, Roberto De Ioris ha 
scritto:
>
>
> > Hello, 
> > 
> > 
> > I'm testing both gunicorn and uwsgi with web2py on my (production) 
> > server with nginx acting as front-end/reverse-proxy. Deploying of 
> > gunicorn is pure simplicity which I like (it reminds me on webpy) and I 
> > can access web2py's admin via https, while having problem to do the same 
> > with uwsgi. 
> > │ 
> > My sites are and, after converting to web2py, will be small/low-traffic 
> > and can raise to medium/medium-traffic in the future, while on my 
> > hosting (ala webfaction) I have limit on the total memory used by apps 
> > to 512MB and number of procs is 50. 
> > 
> > Any idea which WSGI server behave better in such constrained 
> > environment? 
> > 
> > uWSGI certainly looks as very powerful, but maybe it is an overkill for 
> > our needs and brings more trouble with configuration comparing it with 
> > simple deployment via gunicorn? 
> > 
> > 
>
> While the "complexity" of uWSGI in latest times is questionable 
> (documentation improved a lot and the quickstart introduce to basically 
> everything you need), i always suggest newcomers to go pure-python 
> (rocket, gunicorn, flup...) as compilation can be a problem sometimes. 
>
> The problem is that once you start placing apps in constrained 
> environments, you will soon start to face low-level problems (dealing with 
> rss, address space, monitoring), something uWSGI is optimized for (for 
> example you can tell it to reboot after a memory limit is reached and so 
> on) 
>
> In addition to this uWSGI uses lot less memory and supports threading that 
> when you have few resources is a good approach for increasing concurrency. 
>
> The "overkill" definition is really funny (you are not the first person 
> saying it) becase generally uWSGI has hundreds more features than 
> "competitors" but it is the one consuming less resources :) 
>
> And just as a note (from the web2py directory, after having copied 
> wsgihandler.py from the handlers directory): 
>
> gunicorn --bind :9090 wsgihandler 
>
> uwsgi --http-socket :9090 --wsgi wsgihandler 
>
> is it so different ;) ? 
>
> -- 
> Roberto De Ioris 
> http://unbit.it 
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to