Artur
May 10, 2016 06:28AM
Hello,

I'm currently working on nginx limits as a reverse proxy on a Debian box.
My current setup is a nginx configured as a http/https web server (for
static content) and a reverse proxy for node.js processes on the same
server and in future on other Debian boxes.
I was unable to see (while reading the documentation) real hard
limitations for nginx in this setup excepting ephemeral ports exhaustion.
It may be a concern as Node.js applications usually open a websocket
that is connected as long as a user stays connected to the application.
If I understood everything correctly it means that nginx in this setup
will not be able to manage more than about 64k clients connections.
Am I right ? What can be done if I would like to go over this 64k limit
? Could you please suggest a solution ?

--

Best regards,
Artur.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Nginx as reverse proxy scalability

Artur May 10, 2016 06:28AM

Re: Nginx as reverse proxy scalability

Maxim Dounin May 10, 2016 11:06AM

Re: Nginx as reverse proxy scalability

Maxim Konovalov May 10, 2016 11:26AM

Re: Nginx as reverse proxy scalability

Artur May 10, 2016 11:40AM

Re: Nginx as reverse proxy scalability

Valentin V. Bartenev May 10, 2016 11:44AM

Re: Nginx as reverse proxy scalability

Maxim Konovalov May 10, 2016 11:46AM

Re: Nginx as reverse proxy scalability

Artur May 10, 2016 11:50AM

Re: Nginx as reverse proxy scalability

Maxim Dounin May 10, 2016 11:58AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 127
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready