Ameisen Wrote:
-------------------------------------------------------
> requests. To handle multiple concurrent requests, I'd expect nginx to
> multiplex (which it doesn't support) or open multiple socket streams
> to my application, which it also is not doing.
You can't expect something to work if its not supported, such operation is usually done via a restfull api (like Lua) or use a loadbalancer nginx setup with 50 (socket)nodes in it all pointing to the same backend.
Some reading material;
http://stackoverflow.com/questions/7616601/nginx-fastcgi-and-open-sockets
http://michieldemey.be/blog/proxying-websockets-with-nginx-and-socket-io/
https://www.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/
-------------------------------------------------------
> requests. To handle multiple concurrent requests, I'd expect nginx to
> multiplex (which it doesn't support) or open multiple socket streams
> to my application, which it also is not doing.
You can't expect something to work if its not supported, such operation is usually done via a restfull api (like Lua) or use a loadbalancer nginx setup with 50 (socket)nodes in it all pointing to the same backend.
Some reading material;
http://stackoverflow.com/questions/7616601/nginx-fastcgi-and-open-sockets
http://michieldemey.be/blog/proxying-websockets-with-nginx-and-socket-io/
https://www.jayway.com/2015/04/13/600k-concurrent-websocket-connections-on-aws-using-node-js/