On 07.06.2012 08:04, Roberto De Ioris wrote:
http-socket is faster as it does not need to make another connection and
build another request. I do not know if ELB is a buffering server (it will
send the whole request to your instance only after it has get all of the
data from the client) or a streaming one. In the second case you could be
easily DOSsed as a slow request will block a whole process/core. In the
first one use --http-socket to gain memory and cpu.
I want to ask about a little offtopic just out of curiosity...
OpenShift provides hosting of custom user app stack proxied by Apache
(configuration of Apache virtual host could be seen at [1]). Does using
of Apache means that it's safe (and reasonable) to use --http-socket for
uWSGI instead of --http?
[1]
https://github.com/openshift/crankcase/blob/master/cartridges/diy-0.1/info/bin/deploy_httpd_proxy.sh
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
