nginx Window native
Kurien Mathew
kurienmatheww at gmail.com
Tue Jan 24 11:10:35 UTC 2012
Hello,
I tested the Cywin version along with the following additional
configuration settings:
worker_processes 5;
worker_rlimit_nofile 3072;
events {
worker_connections 1024;
accept_mutex off;
multi_accept on;
}
The exact effect of the above settings on the functioning of nginx is not
well understood. But with this configuration I find that multiple workers
do the work and this improves scalability. One problem that I discovered
was that sometimes a connection is not accepted and the following error is
emitted:
2012/01/24 11:45:16 [alert] 15964#0: accept() failed (14: Bad address)
For eg with 2000 concurrent connections about 15 fail to be accepted. When
the client shuts down after waiting, the server sockets go into CLOSE_WAIT
state. They seem to remain that way forever.
Is anyone aware of a way to overcome this problem?
Thanks
Kurien
On Fri, Dec 9, 2011 at 10:38 AM, Ensiferous <nginx-forum at nginx.us> wrote:
> Additionally the Windows version of the event polling which enables high
> performance on unix is called IOCP and is not supported last I checked.
> So you would basically be using select().
>
> Windows support is very preliminary and while I can't speak for the
> development team, I don't think it's supposed to be used for anything
> other than development or testing.
>
> -Martin Fjordvald
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,219822,219825#msg-219825
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120124/4a76e163/attachment.html>
More information about the nginx
mailing list