On Wed, 2 Oct 2013 15:16:23 +0200 "Roberto De Ioris" <[email protected]> wrote:
> 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. Compilation is not the problem here 'cause I installed it via pip on my hosting server without any problem. > 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) Hmm, that's good. > 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. Another 'pro'.. > 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 :) Well, I was mostly thinking if/whether uWSGI's power/advantage is becoming more obvious when serving big web sites with *LOT* of traffic where one wants to squueze last drop of performance. > And just as a note (from the web2py directory, after having copied > wsgihandler.py from the handlers directory): I did that. > gunicorn --bind :9090 wsgihandler I did run gunicorn with: python anyserver.py -p localport -s gunicorn and I was able to access my web site at: http://tld/ without any further port fiddling considering that nginx front-end is sending request to 127.0.0.1:localport, as well as web2py's adming interface via https://tld/ by having previously saved with save_password call. > uwsgi --http-socket :9090 --wsgi wsgihandler Otoh, I was able to use uWSGI in the same configuration with: [uwsgi] http-socket = :localport chdir = /home/some_path/virtualenvs/web2py/web2py module = wsgihandler master = true processes = 4 venv = /home/some_path//virtualenvs/web2py and running: uwsgi uwsgi.ini but could not accomplish same thing trying to access admin interface via https? > is it so different ;) ? Well, *in theory* is quite close, but in practice it was huge difference for me. :-) Sincerely, Gour -- It is far better to discharge one's prescribed duties, even though faultily, than another's duties perfectly. Destruction in the course of performing one's own duty is better than engaging in another's duties, for to follow another's path is dangerous. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 -- 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.
