Welcome! Log In Create A New Profile

Advanced

RE: Why the info 'A worker can handle no more than 1024 simultaneous connections' has been removed from http://nginx.org/en/docs/windows.html ?

Masseau Olivier via nginx
November 17, 2022 11:08AM
Thanks ;)

Maybe it would be nice to add this info on the http://nginx.org/en/docs/windows.html page.
Because without your answer I think I would never have been able to find this information :)

I'm aware that Nginx is not a good idea in production.
But I was asked to evaluate and give evidence from which point the "not so good idead" starts to become a "really really bad idead" :p

========

Hello!

On Wed, Nov 16, 2022 at 03:31:14PM +0000, Masseau Olivier via nginx wrote:

> Previous we could find this very important information on the "nginx
> for Windows" page ( http://nginx.org/en/docs/windows.html
> ) :
>
> Known issues
> ...
> A worker can handle no more than 1024 simultaneous connections.
> ...
>
> Why has it been removed ?
> I struggled a lot understanding why increasing worker_connections
> above 1024 was not working on Windows.

As you can see from the source code repository of the nginx.org site, the relevant item was removed along with the documentation of the poll event method being supported on Windows (introduced in nginx 1.15.9):

http://hg.nginx.org/nginx.org/rev/4795c2ae5066
Added the "poll" method for Windows.

With the poll event method, as long as it is supported by the Windows version you are using (Windows Vista or later), nginx will use the WSAPoll() function, which, in contrast to select(), does not impose a hard-coded limit on the number of connections.
You'll have to use the "use poll;" in your configuration to instruct nginx to use the poll event method, see http://nginx.org/r/use for details.

Note though that with poll there might be other issues, such as failure to report connect() errors till the timeout expires (see https://daniel.haxx.se/blog/2012/10/10/wsapoll-is-broken/ for details; shouldn't be a major issue in case of nginx though, since errors while connecting to backend servers aren't expected to happen).

Also note that Windows isn't really designed as an efficient server platform, and nginx is not really designed to work on Windows. Running nginx on Windows in production setups might not be a good idea.

Hope this helps.

--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-leave@nginx.org
_______________________________________________
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-leave@nginx.org
Subject Author Posted

Why the info 'A worker can handle no more than 1024 simultaneous connections' has been removed from http://nginx.org/en/docs/windows.html ?

Masseau Olivier via nginx November 16, 2022 10:32AM

Re: Why the info 'A worker can handle no more than 1024 simultaneous connections' has been removed from http://nginx.org/en/docs/windows.html ?

Maxim Dounin November 16, 2022 02:54PM

RE: Why the info 'A worker can handle no more than 1024 simultaneous connections' has been removed from http://nginx.org/en/docs/windows.html ?

Masseau Olivier via nginx November 17, 2022 11:08AM

Re: Why the info 'A worker can handle no more than 1024 simultaneous connections' has been removed from http://nginx.org/en/docs/windows.html ?

Maxim Dounin November 17, 2022 03:44PM

RE: Why the info 'A worker can handle no more than 1024 simultaneous connections' has been removed from http://nginx.org/en/docs/windows.html ?

Masseau Olivier via nginx November 18, 2022 03:22AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 102
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready